Download Google Map For Microsoft Phone

Score:
79%

Creating a Google Maps client on a modern Windows Phone faces a number of problems. Firstly, Google will have nothing to do with it, so everything has to be sourced by public APIs. Secondly, most phones will already have HERE Maps pre-installed, often with full offline country maps, making the online Google Maps slower and less convenient. However, the benefits of Google's POI database, StreetView imagery and traffic layers are all enough to make a good client worthwhile, and Clarity has produced just this, arguably blending the best of all worlds together into a seamless whole...

Version Reviewed: 8.7.0.3

Buy Link | Download / Information Link

So again - sorry if the application name (and indeed its icon, if you look in the app listings!) got your hopes up. In fact, there are several apps of this name in the Windows Phone Store (insert my usual rant against Microsoft QA), so make sure you grab the right one. This is perhaps the best of the breed and recently had a big update, so high time for 'Google Maps' (sic) to get the review treatment here.

Available for free, of course, since the source maps are effectively free via Google's (and, as it turns out, Nokia's and Microsoft's) APIs, 'Google Maps' here does add the occasional banner ad, sometimes also asking for donations to keep development going for Windows Phone. In view of the integration and UI work done here, this is fair enough and I wish the developers well.

Jul 11, 2017 1) is there google map on windows phone apps store 2) is there google plus or google chrome on windows phone apps store 07:26 PM Like 0. How to download Google Maps data to your mobile device. Google Maps has made navigation almost-but not quite-trivial for smartphone users. Anyone who has had to wing it on the road when their.

It's worth stating up front that 'Google Maps' takes no prisoners when it comes to sourcing its data. By default it uses the offline maps (from HERE) that you may already have on your device, even while searching Google Maps' POI database and presenting Google Traffic and StreetView data. It's a sign of the maturity of the mapping market in most countries that the various alternatives all 'line up' this accurately, such that you can overlay one data set on the other without worrying about jarring mismatches.

The idea, obviously, behind using your own offline maps wherever possible (and indeed there's a shortcut to this function in HERE Maps on the Google Maps menu!) is that it can save you a lot of data when accessing this system while mobile. If using this hybrid approach upsets you then it's easy to pick the map source you want from the settings menu.

Initial impressions are good, with a set of tutorial screens introducing different aspects of the interface - each can be cancelled or set to pop up later to 'remind', etc.

And then you're into the maps, with the option of '3D' (just a visual effect, tilting the 2D map, obviously, though there are some genuine 3D models of buildings in some cities, with again the hybrid system of Google structures overlaid on Nokia map data!), going to your current location (as determined by GPS or wi-fi/cellular, according to your device settings) or searching by name/category. Interestingly, there's a voice input option, but this isn't Google's rather splendid Maps voice recognition system - it's the standard Microsoft one and does a pretty awful job of transcribing place names.

...looks like this was snapped while the fair was in town!!

Zooming in and out of the maps is with multi-touch, though 'Google Maps' stops short of implementing the 'twist' gesture to rotate things - instead there are on-screen controls to rotate the map, along with a layers/maps master control. This latter proves invaluable as a way of quickly switching map source and turning on and off layers like traffic and transit, as needed.

As usual with Google (and indeed HERE) Maps, red lines aren't good, indicating queuing traffic...

The speed of 'Google Maps' isn't quite there, if you've tried the real thing on a modern Android device - the displays frequently flash with overlay updates and it can take several seconds for a particular view to be fully composed if you have several layers turned on, but be restrained about what you ask for and it's still very useable. The StreetView presentation is the slowest aspect of 'Google Maps' here by far, in that swivelling the viewpoint and generally moving around can be frustratingly slow and jerky.

Using StreetView to locate and find the name of a business I vaguely new was at a particular location. Shame the phone number got mangled by the photo joins...

But it's churlish to complain too much - this is a completely free (aside from any donations you might supply!) application that brings you most of the functionality of Google Maps on Android in an interface that makes sense on Windows Phone - and manages to integrate with the excellent HERE Maps where needed as well.

Very unselfishly, Google Maps spawns out to Waze or HERE Maps, as needed, for example here passing my destination and start position over to Nokia's built-in navigation system.

Google's POI (Points Of Interest) directory is second to none and in addition there's now integration with user photos and reviews, all also accessible here within 'Google Maps' for Windows Phone...

The StreetView imagery and 3D building models are Google's, the map itself is Nokia's - impossible to see the joins!

Some of the search categories, though note that there's guarantee that all businesses will be in the mighty Google database - here the NatWest bank seems to have pushed the right buttons or crossed the right palms with silver, to get its ATMs into the database to the exclusion of other brands/banks!

Who could resist a kitten?(!) Go on, 'Google Maps' is worth a donation, we reckon....

While traffic flow is accurate and detailed, the same can't be said for the 'incidents' pane. On the right, here, the map is centred around an accident on the M4 motorway, yet all the pane wants to tell me about are scheduled roadworks. Hmm....

Although not yet perfect, this is still very much a recommended install, whether it's for emergency look-ups of things that HERE Maps can't find, whether it's to browse through Google's social treasure trove of real world reviews, or whether it's because you like having StreetView at your fingertips.

Download Google For Microsoft

Reviewed by Steve Litchfield at

Meta, Share, Comments

Filed: Home >Reviews >Google Maps

Platforms: Windows Phone 8
Categories: Applications

Please enable JavaScript to view the comments powered by Disqus.

The situation regarding accessing Google Maps on Windows Phone devices is about vendor choice, not browser capabilities.

Let's try this again. Yesterday, a number of reports surfaced that Windows Phone users were unable to access Google Maps in the browser. Instead of reaching the Maps page, users are automatically redirected to the main Google homepage. This is true both for users attempting to access Google Maps from the mobile or desktop view in Internet Explorer on Windows Phone 7.X and Windows Phone 8 devices.

Android Google Maps Download

SEE ALSO: This is Why You Can't Access Google Maps on Windows Phone

Google's official response — as we pointed out yesterday — is that the decision to redirect users away from Google Maps on Windows Phone devices is a choice Google has made. That's because it has optimized the mobile version of its Maps website for browsers that use the WebKit rendering engine. WebKit is the rendering engine that Apple, Google, RIM and many others use on their mobile browsers. Meanwhile, Microsoft uses the Trident rendering engine for Internet Explorer on the desktop and mobile.

While Trident — especially with Internet Explorer 10 — is highly compliant with HTML5, CSS3, JavaScript and other web standards, Google has made optimizations to its mobile maps site that specifically target WebKit. As a result, it's possible that some of those optimizations won't render correctly on a non-WebKit browser, such as Internet Explorer.

As many users have pointed out, Google Maps works just fine on Internet Explorer for the desktop. Microsoft's official comment is that Internet Explorer 10 uses the same rendering engine as Internet Explorer on Windows Phone 8. If IE 10 can render a page, Windows Phone 8 should be able to render that page equally well.

Believe it or not, this is still in line with Google's own comments on the matter. The desktop version of Internet Explorer serves the standard version of Google Maps without a problem at all. This is about the mobile website.

When I tried to explain the situation yesterday, I failed to properly clarify that this is not about whether or not Internet Explorer is capable of displaying Google Maps. Instead, it's about Google's decision not to support non-WebKit mobile browsers.

To wit, changing the user agent on the Windows Phone simulator to something that doesn't say Windows Phone or identifies itself as Internet Explorer for Windows Phone renders the desktop version of Google Maps without a problem.

I should also clarify that Google is going one step further and also blocking access from the 'desktop' mode on Windows Phone. To me, this is going too far. It's one thing to not support the mobile view; it's another to remove to ability to access the site even with the desktop view in place.

It's Not Just Windows Phone

Windows Phone isn't the only mobile platform that is experiencing redirects from Google Maps. In non-WebKit browsers on Meego and Symbian, I saw the same results. I also re-confirmed these results with a user agent switch on a desktop browser.

Interestingly, Firefox for Android and the FirefoxOS simulator both work with Google Maps — at least for now. This is despite the fact that Firefox uses the Gecko rendering engine, not WebKit. The last time I tested Firefox for Android back in June, I ran across a number of different errors accessing Google-specific mobile pages. It remains to be seen if Google will continue to support its WebKit-only views on Firefox for Android in the future.

Google Should Follow Its Own Best Practices

While I respect Google's right to block mobile access from non-WebKit browsers, I do wish the company would have chosen to follow its own best practices when doing these redirects.

Download Maps For Google Maps

According to its own best practices, Google discourages user-agent sniffing to control what type of website is displayed. Instead, Google (and other web experts) recommend that web developers detect for specific feature support, rather than the user agent.

What I suspect is really happening is that Google is phasing out support for its WAP-based mobile maps and is focusing all of its mobile efforts on WebKit. As a result, non-WebKit (or whitelisted) browsers on mobile devices are going to lose access to Google Maps, regardless of how capable the browser rendering engine may or may not be.

Could Google Maps for Mobile Work on Windows Phone?

As earlier tests have shown, Google Maps, at least the desktop view, appears to work just fine on Windows Phone.

Download Google Map For Microsoft Phone Free

What I have not been able to test and confirm is how well Google Maps would work on a Windows Phone device if the user agent was changed to WebKit instead. While spoofing a user agent string is generally discouraged behavior, this would be a way to look at how the WebKit-optimized mobile code runs on the non-WebKit IE browser.

I suspect there are some very real usability problems — based on my own experiences with WebKit-optimized mobile sites on Windows Phone — but I'd like to confirm the situation one way or another. If you have access to the Windows Phone emulator and want to try out that sample app, let me know what you find out. As soon as I'm back in the office with a Windows dev environment, I can test this myself.

Ninbutton