I used to work on Google Maps and am still friendly with a number of GMM developers, so take this for what it's worth.
Quote:
Originally Posted by daveT
Is the maps app on iPhone 5 really as bad as HN is making it out to be? I feel like it is skewed by Apple Haters, but even mainstream media is tossing poo at the company.
From seeing some of the side by side quality comparisons (actual search quality metrics as used within the company, not just the cherry picked images being used right now that make the Apple maps look terrible), yes, it really is pretty bad. You might be lucky and have the features you use work correctly in your particular locale, but overall it's a pretty big regression, especially outside the US.
Basically maps and/or local search is a very difficult and data intensive problem, and takes a ton of infrastructure to do right. You get the first ~60% or so for free, but there's no good way to scale to get the rest of the data without driving a lot of cars around or doing some massive crowdsourcing, and a mapping system is pretty sensitive to getting that long tail right. Google's been collecting that data for years because of Street View, but it's been a billion dollar project.
Here's an article about some of the process involved. I'm honestly really surprised it got published, given how secret GT was a few years ago. Take a look at the base TIGER layer and see how it compares to reality, and then imagine doing all those fixes for every street in the US, and it gets way more complicated once you start doing other countries as well, and that's just the map layer. Local search is an almost orthogonal problem of probably lower scale but possibly higher complexity.
http://www.theatlantic.com/technolog...ything/261913/
Quote:
I doubt this is enough to place a major dent in iPhone sales. After a few months, people will forget the emotional reaction to it, and they won't want to fork over the money to buy a new smart phone anyways, thus the iPhone cycle reboots for another iteration or two.
Very likely true.
Quote:
Originally Posted by daveT
This had to have started under him. It's not like you can toss together a map app in a month. Jobs wanted to crush Android, so from a business perspective, if Apple could create something that is better, then that is one more reason to switch over. Maybe with all the lawsuits and Jobs' promise to go nuclear on Android, Google stuck up their middle finger to Apple my refusing to release a new app.
Jobs, mind you, was very risky and presented his fair share of flopsom.
Edit to add: I'm not calling the new maps flopsom sight-unseen, just saying that he wasn't immune to mistakes. I also agree that there is some end game here as well.
Google never wrote the iOS "Google Maps" app, it was always controlled by Apple engineers using the Maps API, for various complex contract and control issues. Supposedly that's part of why iOS maps lagged behind Android maps, since the public maps API lags behind what's available internally. I think it's almost certain that Google has written their own maps app by now and it's being held up in review indefinitely. The Google/Apple relationship is such that pretty much any Google iOS app doesn't go through the usual app review process. (see Google Voice)
Basically any article you read about this whole kerfuffle is going to be wildly inaccurate, or at the very least, missing a lot of context.