So, iOS 6 is upon us and people are going to start getting their new iPhones this week as well. What they’ll soon (maybe) realize is that Maps for iOS is no longer powered by Google. And it sucks something fierce, and yes I’m using iOS 6 GM.
I’m not going to go into tons of technical detail as to why this is, but let me just say that when consumers are used to an experience for oh, five years, and you all of a sudden change it, people are going to be angry or confused. I’m betting on both happening with the Maps app.
Apple decided to build its own and no longer work with Google, which has a world-class Maps product. That’s cool, and it’s Apple’s decision to make. However, when you think about those consumers, the decision seems odd. Sure, there’s a lot of data to be had with your location, and Apple wants to own it. Right on, fine. But the best-of-class experience, which Apple loves to tout, is simply not there with Maps.
The no-show for a Google Maps app in the App Store ahead of iOS 6 is puzzling. You’ve got about 28 minutes, Google!
—Martin Bryant (@MartinSFP) September 19, 2012
If I were Google, I wouldn’t launch a native Maps app for iOS 6 for at least six months, and here’s why:
Let consumers experience what a really bad map experience is like and let them get angry at their beloved Apple. Let Apple explain why their Map App isn’t up to snuff yet, that it takes time and talent to make something absolutely wonderful. Let the consumers ask Apple why they kicked the experience that they were used to for five years out of the phone completely.
And then…after a few months, let Google swoop in and save the day with a mind-boggling and amazing iOS 6 native Maps app. Would Apple even allow that, or will it break out its “core functionality detector”?
That’s exactly what I would do if I were Google. But I’m not. Apple, you really shouldn’t mess with things that work, I hope that the next version of Maps on iOS 6 is magnificent. Otherwise, your move Google. Until then, you can use the mobile version in Safari.
