Google may have an iOS mapping app in the works after all

This is despite chairman Schmidt's remarks to the contrary on Tuesday.

Google Chairman Eric Schmidt told the press on Tuesday that his company hasn't "done anything yet" to submit its own competing mapping app for iOS. But sources inside the company told the New York Times that a Google Maps app is indeed in the works, and is slated to be ready by the end of the year.

Most Ars readers know that Apple rebuilt its Maps for iOS 6 from the ground up, replacing the mapping and routing information it licensed from Google with its own database culled from multiple sources. While the new Maps app looks nice, and finally includes turn-by-turn navigation, the accuracy of the map data itself has proven less than stellar. And Apple's solution doesn't address navigating by public transit, a common use case for urban users.

Frustrated users who wanted the old Google Maps experience expected Google to simply make its own app like it did for YouTube (when Apple removed its largely neglected, in-house-developed YouTube app from iOS 6, Google stepped up to replace it). However, Google has so far simply pointed iOS users to the Web-based Google Maps, and Schmidt seemed to downplay the idea that the company was building any native app at all.

But that's reportedly not the case, according to unnamed sources "involved with the effort" to make a Google Maps app for iOS. The company is said to be making such an app for iPhone and iPad, these sources told NYT, and it should be ready in the coming months.

The effort was delayed in part because Apple and Google had a contract to license Google Maps data for iOS that didn't expire for at least another year. According to The Verge, Google was as surprised as the rest of us when Apple announced in June that iOS Maps would use its own mapping data, including 3D "flyover" views powered by its acquisition of C3 Technologies. While the writing on the wall suggested Apple would eventually begin using its own mapping data at some point, Apple's decision to ditch Google's data earlier than expected "sent Google scrambling" to develop its own app. Not surprisingly, three months just wasn't enough time to get the app ready for iOS 6's launch.

I find it hard to believe Google is "scrambling" to get a Maps app out on iOS. If I were Google I'd take my sweet time and let the bad publicity sour iOS 6 and the iPhone 5 for as long as possible, while making Android look more attractive.

I wouldn't be shocked if it was already done. Apple showed off Maps well in advance and Google obviously knew what would happen. I think it has more to do with making sure Apple gets some bad PR and build up Google Map's reputation.

Google Maps sucked on iOS. Hopefully they will do more than release the same basic app from before (yeah Apple wrote it, but it was little more than a GUI for the Google data).

Although this information may not be publicly available, I wonder what the differences are between the code for the iOS 5 Maps app and an independently released Google Maps app?

Presumably Google would have access to most of the code for the native iOS app as a partner involved in the original development, though their partnership agreement would likely preclude Google from re-using this code, it should not be very difficult for the original engineers to re-code for independent release.

I second the story Author that Schmidt was likely just stalling for time.

Edit: post-script.

One more sneaky thought, what if it is actually Apple that is delaying the approval of an already submitted Google Maps App in order to focus their customers on iMaps?

I find it hard to believe Google is "scrambling" to get a Maps app out on iOS.

Huge core funds, crowd sourcing, a massive installed base, and the market-based plugin system Apple is utilizing means that map data is likely to improve rapidly. In some locations it's already better then the old Google Maps ever was, though in others of course it's significantly worse. Given time though, it's going to become good enough everywhere, a ecosystem may come out of it, and at that point it'll be thoroughly entrenched. Google has a relatively limited window of opportunity to try to get as many iOS users as possible back into their own ecosystem. The best time is immediately, while the brand new entrant, despite being the native default, still is firmly 1.0 with all the rough edges and blank spots that entails. It's also the time when the media and general attention is highest.

But give it 3-6 months and it'll become exponentially harder. The native maps will get much better. 3rd party plugins will start to be everywhere. The media will have long since moved on (just as with the antenna thing), people will have gotten used to the change. If you think anyone can afford to simply rest on their laurels in this market you are dangerously mistaken, particularly in the case of Google whose entire business model depends on data gathering and advertising.

There’s a big chunk of this Maps kerfuffle missing and it reeks of corporate politics.

Perhaps Apple led Google to believe they would be seeing out their remaining year hoping to catch the Maps team off guard, delaying the inevitable native Google Maps App and forcing iOS 6 customers to use the new mapping solution thus getting a kickstart the crowd sourced data they so desperately need.

On the other hand, perhaps Google knew what a flap there was going to be and are purposely holding off releasing an App in the hopes of getting disgruntled iOS users on to Android over the holiday season. Then releasing the native Google Maps app in January, still superior to the inevitable 6.1 update and looking like a hero.

As a shareholder in Google either of those scenarios are preferable to the idea Google was caught unaware of Apple’s intentions; Apple Maps was perhaps their most telegraphed major software initiative in years.

When did Google know that Apple was dropping the built-in YouTube app? I don't recall, but it would be surprising that they didn't know about both at the same time.

I don't recall either, but I heard the news about Apple dropping youtube app July on NPR radio. I didn't heard anything about dropping Google map until Apple Con this month. From this article, Apple still has a year+ left on their map license. So I can reasonably assume it was Apple trying to surprise Google while Google in middle of adding new feature to their map app.

I find it hard to believe Google is "scrambling" to get a Maps app out on iOS. If I were Google I'd take my sweet time and let the bad publicity sour iOS 6 and the iPhone 5 for as long as possible, while making Android look more attractive.

I disagree and that won't be likely, but personally I'd hope so just so Apple can have more time to create a robust mapping platform.

Why won't Google drag their feet? Simple. The usage patterns of iOS owners has been a gold mine in feeding Google mapping data and helping them improve and enrich their contextual data. It wouldn't make sense to cut off that flow of information.

The longer Google delays, the better chance Apple has to compete more effectively. This is a time when Apple has to put in an herculean effort to not only ensure that it has access to that kind of mapping and location information but also make sure its doesn't find itself in a position where a competitor can adversely harm its platform (see earlier Microsoft).

And no, an app isn't already ready and being held up by Apple. We heard about Google Voice, we'll certainly hear about Google Maps.

I wouldn't be shocked if it was already done. Apple showed off Maps well in advance and Google obviously knew what would happen. I think it has more to do with making sure Apple gets some bad PR and build up Google Map's reputation.

Google Maps sucked on iOS. Hopefully they will do more than release the same basic app from before (yeah Apple wrote it, but it was little more than a GUI for the Google data).

I would be. Apple is relying entirely on its userbase to finish the maps datasets for them. Getting Google Maps back out would slow down the progress Apple is making from all the user corrections, letting that bad PR last even longer.

Of course they could delay to make Android look better, but I really wonder how many people would switch just for a maps app...

How is google maps for mobile monetized? It seems like in the current situation the only way google earns from the service is that it drives users toward other highly monetized Google products. Without the Apple license payments, seems like GMaps for iOS is a money loser, unless the charge for it or insert ads. I interpreted Schmidt's statement as a recognition of the reality that iOS users are on there own when it comes to maps unless Apple wants to pay for it for them.

Why would Google develop this? Do anybody really believe that they will charge for it, or put ads on their maps?

Google was hardly likely to ignore the opportunity to sell advertising to all the millions of iPhone users.

Ads in mobile Google Maps? Not gonna happen.

Not ads, but definitely more "sponsored" results.

I was under the impression that Google got paid in some way for showing you restaurants, shops etc in Maps.

I think they get paid when they show you a sponsored result as the first pin instead of what you actually searched for. That's been happening for a while. They also find the local searching data they get from people using the app quite valuable.

Apple showed off Maps well in advance and Google obviously knew what would happen. I think it has more to do with making sure Apple gets some bad PR and build up Google Map's reputation.

You're making the same mistake as kevin_luke, and at least presumably Google is a lot more on the ball then either of you. A minor bit of bad PR isn't going to matter strategically one bit unless Google can actually capitalize on it. If Apple really never did touch their Maps app again and no 3rd party did anything with it then sure, it'd become an enduring stain and a real issue. That however, to put it mildly, seems doubtful. In reality it'll probably get ironed out to the point of being good enough relatively quickly, at which point the general public will promptly forget about it. Assuming Apple can actually make it better somewhere they may even get some positive press out of it in the end for being "visionary" or something.

No, this sort of PR has a shelf life. The only way to make it strategically matter is to be ready to use it, as quickly as possible, in order to shift the overall landscape longer term. If anything, it's as likely to be the opposite of what you're suggesting: Apple may have worked hard to keep it secret specifically to try to keep Google or others from being entirely ready. Apple had to know that 1.0 would have tons and tons of rough spots, and there's no way to really get all that sorted out without getting the thing out there. It's in Apple's interest that, during the fragile birthing period, there is as little competition as possible. People may grumble, but if there isn't anything else that's particularly great and free most will just suck it up for a while. If "a while" is long enough to start getting it updated and smoothed, then the rough transition can be ridden out. The worst case would be if an awesome Google Maps were available at launch. That's when lots of people might just vent their immediate frustration and swap without ever giving Apple maps a second look.

I find it hard to believe Google is "scrambling" to get a Maps app out on iOS. If I were Google I'd take my sweet time and let the bad publicity sour iOS 6 and the iPhone 5 for as long as possible, while making Android look more attractive.

I have no data to back this up, but I suspect Google would see more revenue potential from ios users than from Android users.

Googles shareholders would not appreciate Google leaving that money on the table.

How is google maps for mobile monetized? It seems like in the current situation the only way google earns from the service is that it drives users toward other highly monetized Google products. Without the Apple license payments, seems like GMaps for iOS is a money loser, unless the charge for it or insert ads. I interpreted Schmidt's statement as a recognition of the reality that iOS users are on there own when it comes to maps unless Apple wants to pay for it for them.

Why would Google develop this? Do anybody really believe that they will charge for it, or put ads on their maps?

Think big picture. Mapping is literally a way of describing the world to someone else. Its a huge source of information and a source of power and leverage.

An example would be doing a local search for coffee shops and a sponsored result coming in as well for Starbucks.

Just like Google Search influences and shapes what you know about the web and the world, so would mapping. Think about the last time you used a yellowbook or an actual map.

Although this information may not be publicly available, I wonder what the differences are between the code for the iOS 5 Maps app and an independently released Google Maps app?

Presumably Google would have access to most of the code for the native iOS app as a partner involved in the original development, though their partnership agreement would likely preclude Google from re-using this code, it should not be very difficult for the original engineers to re-code for independent release.

I second the story Author that Schmidt was likely just stalling for time.

Edit: post-script.

One more sneaky thought, what if it is actually Apple that is delaying the approval of an already submitted Google Maps App in order to focus their customers on iMaps?

My understanding was that Apple pretty much wrote it on its own. When the original iPhone came out, Google was as shocked as anyone that their mapping data was being used for iOS.

I find it hard to believe Google is "scrambling" to get a Maps app out on iOS. If I were Google I'd take my sweet time and let the bad publicity sour iOS 6 and the iPhone 5 for as long as possible, while making Android look more attractive.

I have no data to back this up, but I suspect Google would see more revenue potential from ios users than from Android users.

Googles shareholders would not appreciate Google leaving that money on the table.

There's long game and there's short game.

Most people are so focused on the short game they don't see that the light at the end of the tunnel is actually a train.

Short term leveraging ios users does help Google, long term, steering as many of them as possible gently toward the Android ecosystem is definitely in Google's interests. Apple is actively doing as much as possible to deny Google's survival in the mobile space.

I give Google enough credit to know Apple has been buying mapping companies the past couple years. It doesn't take a genius to realize Apple is going to release their own, especially when they highlight it during the iOS 6 demo a short time ago. It's common sense that Apple would only want their mapping software by default. The closest thing to a curveball would be Apple not renewing the contract and offering the app as a stand alone in the market (which seems highly unlikely as it is against Apple's own motives).

Google is either ran by idiots with no foresight or they are waiting to capitalize on the bad press. There is a sweet spot between the press talking about it, users getting upset, and the quality of the app improving. It would be sometime in a month or so.

Lastly, does anyone really think Apple would reject the app? That would open a whole new can of worms. (the replicating functionality rule isn't so much a rule before, only browsers still have a heavy restriction based on security - and possible Apple wanting to make sure Safari and iOS dominate mobile marketshare)

Although this information may not be publicly available, I wonder what the differences are between the code for the iOS 5 Maps app and an independently released Google Maps app?

Presumably Google would have access to most of the code for the native iOS app as a partner involved in the original development, though their partnership agreement would likely preclude Google from re-using this code, it should not be very difficult for the original engineers to re-code for independent release.

I second the story Author that Schmidt was likely just stalling for time.

Edit: post-script.

One more sneaky thought, what if it is actually Apple that is delaying the approval of an already submitted Google Maps App in order to focus their customers on iMaps?

My understanding was that Apple pretty much wrote it on its own. When the original iPhone came out, Google was as shocked as anyone that their mapping data was being used for iOS.

What? Google and Apple were buddies before the iPhone came out, and more importantly, before the huge design shift in Android. That's why Jobs felt so betrayed and wanted to go thermonuclear.

Most people are so focused on the short game they don't see that the light at the end of the tunnel is actually a train.

Short term leveraging ios users does help Google, long term, steering as many of them as possible gently toward the Android ecosystem is definitely in Google's interests. Apple is actively doing as much as possible to deny Google's survival in the mobile space.

The "long game" won't last long enough to push many people onto Android. Apple's maps will improve over time. And considering how much Apple's maps have improved in China, it seems more likely that the increase in Chinese marketshare would more than make up for any loss in the US and Europe.

If you think Google's long term goal is to use this as a way to gain marketshare for Android, than Google has already lost. They need to be focusing on China, an area where they are not a significant player.

Google is just doing what everyone with a sane business mind would do: Let it simmer a bit, then have all hail Google for finally and with big press coming with a map app for iOS 6.

I mean, there will be many articles written, there's bad press for Apple and there will be good press for Google.

Anyway, I doubt that this map app fiasco will be enough to "sink" Apple. It just shoots a tiny hole into a very large ship and it's not the first and not the last one. Still, Apple has some flaking paint right now in the public mind. Things won't change very fast, but it's obvious they're changing. No need to hurry.

1. Eric Schmidt is the Chairman of Google, not the CEO anymore. That would be Larry Page.

2. Of course Google wants to have a Google Maps app onto iOS ASAP. The data mined from iPhone users are invaluable to the data for all Google Map users. Just think traffic data, and how much better it would be if Google still gets that from iPhone users. And there are A LOT of iPhone users.

3. I haven't used the iOS Maps extensively, but from the time I have spent with it using my friends' devices, it is not as bad as the internet would have me believe. Or at the very least, it is definitely improving. (e.g. Berlin is no longer in Antarctica)

4. As someone very tied down to Google's ecosystem, I like the fact that Apple is making their own mapping app. You can see Google rolling out features and support at a much more rapid pace for the web and Android maps now that there is a credible competition. (Yes, Bing Maps and Nokia Maps may have better mapping data, but iOS Maps has a better reach and replaces Google Maps.) I hope this means more innovation, less litigation. (Isn't it way past time to integrate Google Maps with Google Earth?; Or providing turn by turn navigation to iOS users, and to more countries[Note that iOS Maps turn by turn navigation is already supported in more countries than Google Maps turn by turn navigation] {Particularly ironic as Google are the ones who are known to roll out incomplete, beta, products, but the roles have reversed between Google and Apple, at least with regards to the Maps apps})

5. Could the reporter do some investigating and tell us if the mapping contract between Apple and Google actually prevents Google from releasing a competing Maps app so long as it is active, or if Apple releasing its own Maps app voids the contract, or if it is only that Google did not expect Apple to launch their own Maps app so long as the contract is active.

Most people are so focused on the short game they don't see that the light at the end of the tunnel is actually a train.

Short term leveraging ios users does help Google, long term, steering as many of them as possible gently toward the Android ecosystem is definitely in Google's interests. Apple is actively doing as much as possible to deny Google's survival in the mobile space.

The "long game" won't last long enough to push many people onto Android. Apple's maps will improve over time. And considering how much Apple's maps have improved in China, it seems more likely that the increase in Chinese marketshare would more than make up for any loss in the US and Europe.

The long game is what happens once Apple has effectively cloned the functionality of Google's offerings and shut them out of the iOS ecosystem, or effectively done it.

Android was created because Google saw what was potentially coming once locked down gateways were used by others to control Google and users and make sure the gate keeper got their cut or that Google was all together locked out.

With the amount of time Google Voice Search has been in the app vetting process for iOS, I'd be skeptical that even if Google Maps WAS ready to go, that Apple would fast-track it into the App Store. Add to that, the Voice Search app seems directed at adding Siri-like functionality to devices that aren't slated for Siri, but the Maps app appears to be aimed at competing with/replacing the native Maps functionality in iOS6 altogether...

The long game is what happens once Apple has effectively cloned the functionality of Google's offerings and shut them out of the iOS ecosystem, or effectively done it.

Android was created because Google saw what was potentially coming once locked down gateways were used by others to control Google and users and make sure the gate keeper got their cut or that Google was all together locked out.

I'm sure there's room for more than one interpretation. Alternately, Android was created to move the OS marketplace from a pay model to an advertising supported model. In that case, the long game is what happens when Google's "free" apps and OS completely displace the offerings by companies who sell the products rather than the advertising.

Not surprisingly, three months just wasn't enough time to get the app ready for iOS 6's launch.

This is surprising to me.

I mean, google shouldn't have a shortage of talented people they could have thrown at this, and they have experience making both mapping apps, and iOS apps (Even if they somehow had nothing to do with the programming of the iOS maps app, which I doubt). I'm very surprised they couldn't get something put together by now. Especially since this being likely wasn't exactly 'news' 3 months ago. (It being definite may have been, but a basic project plan should probably have been drawn up beforehand too, since the writing was on the wall.)

So, yeah.. 6 months to develop a 'port' of the android maps app, or an 'update' of the code for iOS maps they probably have from when they helped develop it in the first place... seems long to me. I mean, it's not like they should be having to invent anything here, just roll it all together and polish it.

Granted, I know google can move.. oh, lets be nice and call it "Deliberately".. But still, a 'beta' would have been a nice gesture to iPhone users.