Google Maps on iPhone shows iOS 6 Maps where to go
Summary: I didn't think iOS 6 Maps were that bad, but turn-by-turn navigation on Google Maps is so good there's no way I'd deliberately launch iOS 6's Maps app again...
I meant to write this piece yesterday, but events conspired against me doing so. And today I'm wondering whether it's worth writing a comparison of the turn-by-turn navigation features on Google Maps for iPhone and iOS 6 Maps at all.
You see, the problem is that "Google Maps v iOS 6 Maps" is perhaps the most unfair fight in the history of the technology industry. What you have on one side is an inebriated, sloth who's having a particularly lazy day. On the other side you have Godzilla, who's in a bad mood because he's caught his wife sharing flirty texts with King Kong. There's no drama here, no cut and trust of two well-matched competitors. Google Maps squashes iOS 6 Maps without even being aware that it's doing so.
Satnav
Personally, I didn't have too much of a problem with iOS 6 Maps. I was expecting an unmitigated disaster when I upgraded to iOS 6, but in the areas I used it iOS 6 maps successfully rendered roads and other things roughly where they were actually positioned in space. But I did discover the beauty of having turn-by-turn directions on my phone. Although I'd used turn-by-turn on a mobile for a bit during the brief period where I owned a Lumia 800, since 2003 I've used a dedicated satnav unit in the car. About a day after I first used turn-by-turn on iOS 6 Maps, I took the satnav out of the car and resolved to sell it on eBay.
The maps on Google Maps are clearer, and that's probably enough in and of itself for Google to win the fight. You're supposed to be driving a car. iOS 6 Maps are "information-poor" -- it's basically a white space with some roads rendered on it where the roads are. Google Maps renders much more subtle information that mirrors the physical space that the driver is in. Google actually does cartography. I'm not at all sure what Apple's mapping software people are doing. Plotting points on a map isn't cartography.
Here's two screenshots of the same tricky turn on a road in the UK. What's happening here is that there's a dual carriageway, but the median between the two carriageways is full up with mature trees. The Google Maps image gives you more of an indication that there's greenery. All the iOS 6 Maps one is doing is telling you that there are some roads. With the iOS 6 Maps one there's a bias towards you having personal pre-knowledge of the area that you're driving through. Google Maps assumes that you don't know where you are. Google Maps also renders roads in the correct colour. This sort of road in the UK is signposted using green colouring, which Google Maps uses. For UK users, iOS 6 Maps look like they're obsessed with everything being a motorway (which happen to be blue).

Another thing that Google Maps will do is allow you to fiddle with the map view during navigation. Oftentimes you can be in a situation where you have two possible routes home and you know one is filled up with traffic and the other relatively clear. You might want to inquire whether the system is routing you through the one without traffic. In this screenshot all I had to do was pull over, twiddle with the maps to see that it was taking me on the route to the right rather than the more straight-on route. (I happened to know the straight-on route was rammed with traffic.) On iOS 6 Maps you can do this, but it's more fussy.

That's why Google wins this fight. One glance from that fantastically clear rendering and you know what's going on and you can park the phone back in your mental periphery and get on with your day. Turn-by-turn directions on iOS 6 Maps is fussier to use and has maps which are substantially less clear. Perhaps counter-intuitively, it's a lack of information that makes them less clear.
There are some other points too. iOS 6 Maps uses the phone's onboard speakers for directions. When you plug the phone into your aux port on your car stereo it redirects the speakers to that. So if you're listening to the radio, you get no directions because the aux port is not active. Plus, when you're listening to audio from the phone itself, the situation gets stupid. Say you're listening to a podcast with a low recording level and the volume is cranked up. At this point when the directions are read out they are basically screamed at you. It's not pleasant.
Google Maps plays the directions through the Bluetooth interface in the car. This means it works when you're listening to the radio, and whatever you were listening to before gets nicely muted and the directions read out to you without yelling. It's much nicer.
All of these points tell us that not only does Google understand mapping, someone actually "dogfooded" this stuff before they released it. If you're trying to use your iPhone to get around in the car, Google Maps simply offers a better experience.
Where next?
If we look back at the products, I find myself wanting to say that they are both as good as one another at the actual task of planning the route and guiding you through it. Then why the sloth v Godzilla simile above? I think it comes down to the fact that Google Maps is noticeably better in a way that makes iOS 6 Maps irrelevant. And it's this irrelevancy that deems it this future:

(Thanks to the parody Twitter account @ios6maps for that moment of comedy gold.)
And then you have to wonder where do we go next. I'll never use iOS 6 Maps again, not out of malice, but because there's no particular point to do so.
Well, until Google Maps makes some boneheaded move and manages to alienate its customer base. That's what makes living through this current phase of the technology industry's life so interesting. Before Apple mucked up iOS 6 Maps we took Google's mobile mapping stuff for granted. When it was reintroduced on the platform last week, the feel on Twitter was like some alien race had some down and gifted humanity with a compound that gave us all everlasting life. Apple's cackhanded rollout of their mobile mapping stuff has simply wrapped up and gifted the whole market to its erstwhile partner without any clear indication of exactly when Apple going to get a new opportunity to fight back on a more even footing.
But there's always something going on. For example, today's tech business immolation seems to be Instagram. An opportunity for someone, even if it does stink for any user with an emotional investment in Instagram.
What do you think? Post a comment, or talk to me on Twitter: @mbrit.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Move on...Apple Maps vs. Google Maps is yesterday's news
So which one is it? The author seems to have the pros and cons a bit mixed up. But as long as the conclusion is makes it 1:0 in favor of the Google Maps it’s all good. We all know where the UK stands when it comes to Apple.
Translation
Thank you.
Wow!
iOS maps also plays through Bluetooth.
Biased
Take Android, when it came out it was garbage. Two years later it is much improved. The same will happen with Apple Maps.
If/when Apple maps is better, we'll use it.
iOS Maps work fine in the NY metro area
The issue is why Apple pulled the trigger on their own maps app now.
It was all about ego for Apple and not what was best for their users. That's what happens when you think that since you're worth 100 billion dollars you can do whatever you want and get away with it. Well, not so fast.
Innovation? Not so much...
Unless you call jazzing up features others have had for a while and making them cool "innovation"... which I certainly would not.
Apple doesn't innovate, but they DO a fantastic job of polishing ideas and concepts someone else comes up with and packaging them in a really appealing way.
You forgot the 5th row
Best quote of the day
I can just see Tim Cook's quote in response:
"apple maps is accidentally launched by millions of users every day. That's success."
Confusing
The iOS Maps image shows to turn right in 0.2 miles which seems to be the intent for the route. Google Maps image suggests (to me) to turn left in 0.1 miles? I don't really see the Google image clearly showing the median is filled with greenery. iOS Maps works fine with Bluetooth. Why would you have anything plugged into the AUX jack if you have Bluetooth?
Also, what Matthew called "information-full" is what Apple calls "clutter",
Oh right, apple said it.
Agreed
On the turn left, good catch.
On my 3GS my choice for voice turn by turn is MapQuest.
Established products typically do perform better.....
Google Maps needs to go metric
iOS beats Google Maps in my test
iOS nailed it, start to finish. On the way back i took a different route to check Google's rerouting algorithm. Google maps had me trying to make a U-Turn for 5 miles AFTER the reroute and would have added 10 miles to my trip.
The algorithm Google maps uses for rerouting is terrible. iOS maps was spot on.
There is more to iOS maps than you think. I also tried Navigon on the same trip another time. SAME AS iOS!!
Conclusions:
Google turn by turn has a better voice
Google's reroute algorithm didn't work well at all
iOS had better information and worked in the lock screen
I am sticking with iOS maps.
I'd like to see more analysis like this
A goog analogy would be the Google Docs app on iOS. Obviously, this app uses Google's cloud solutions, rather than those of Apple (ie. iCloud), so it works in a very different way. Third party developers, meanwhile, can opt for iCloud APIs within the iOS SDK.