All of this in addition to users reporting erroneous results.
For example, they know how dense their geo-data is; where does the volume of queries most exceed the existing density of data? Which queries actually result in someone following instructions to their terminus, and then not requerying again for a while?
Also: while Apple doesn't have a toolbar reporting every query and click into Google Maps -- as with the Google-Bing search results dustup of February 2011 -- they could be using their own automated process to trickle queries into Google Maps APIs and highlight major discrepancies with their own answers, for engineer/data-entry attention.
Cool idea; I wonder if it'd run afoul of copyright laws though.
I'm not in this domain, but they do have the location of millions of phones as they move around during the time the Maps app is open. This could solve problems like adjustment of roadway locations, finding one-way streets, identifying highly-used locations. If people take a different route than the one recommended, this is also a clue.
The location information would also provide a focus-of-attention mechanism (concentrate manual effort along oft-driven routes).
I'm not familiar enough with their privacy rules to understand what portion of this data was already available to Apple versus stuff that is only available on the server side.
Then I understand the release and iterate strategy, and I'm sure it applies in many situations. But when you are Apple and have painfully built a reputation of releasing only great products, you may want to think more than twice before crippling your star product, even if it's just a little.
Weird as it sounds (not being sarcastic), I think people will actually report problems, especially in their own neighborhoods or places where they travel and know well.
Your maps is rubbish, I couldn't find the park, where is streetview too!
They will then have to have someone look at that data, try to find the area, a park nearby, compare with whatever licensed satellite data they have, and try to redraw that section, or they have to request new data from tomtom, wait a year, and hope it is fixed. That is a huge task, and not one I'm confident Apple will ever manage to pull off. The satellite data they have put into the app is appalling so if they try to use that as a reference...
And that's for the 0.5% of people who bother to report a problem - the rest will just lower their opinion of Apple and look at other solutions next time they're shopping for a device.
They would do well to make that more prominent especially in the short-term to better handle their growing pains here, but it is a quite solvable problem. Unfortunately for Apple, Google has invested nearly a decade and who knows how much money into Maps (they were straight-up paying cash for business listings at one point, and may still do so) - so the standard with which they're competing is extremely high.
iOS maps is in the same position that AndroidOS was in a year or two after the iPhone appeared. Substandard in comparison, largely functional with big gaps, but an expectation of quick improvement.
Then they sell you and your data to advertisers.
I'd rather pay for something than be sold.
But you don't just rip out something millions of people depend upon for a function as critical as safe navigation in unfamiliar areas and replace it with something that has constant, pervasive issues performing its basic operations. A custom Maps application and dataset is a good business move, but you have to make sure it's at least a minimum viable product before you do the kind of rollout that Apple has done.
When Google replaces Gmail with the shinier "Googmail" and 25%+ of mail to the new service comes back undeliverable, and there's no reasonable method to revert to plain old Gmail, you'll have a comparable quagmire. The fact is that while Apple's Maps may occasionally work sort of well, the failure rates are unacceptably high; too high for anyone to trust the program any more.
It will take years to undo the damage from this, and I fully expect a good portion of people to swap iPhone for Android as a result.
How many did you pay for?
Apple sells an experience — the whole package. They always have. That's why Antennagate, a hardware issue, and Maps, a software issue, are equally frustrating and newsworthy. Apple proposes to remove the hardware/software distinction and deliver a magical device that just works.
Maps no longer just work for many people. And that's the problem with magic. It's very brittle. The clock strikes midnight and everyone turns back into a pumpkin, the ball is over. And so many people are frustrated, because they pay a premium for this abstraction, this magic, and it has disappeared, and that annoys them, and it scares them, because if Maps can stop working when it used to work, then so can my Phone, and my Email, and all my kids' baby pictures, and overnight, Apple's customers no longer feel in control.
I like the new maps (I live in Austin, the data seems pretty solid.) But this letter is a big deal. For the first time that I'm aware of, Apple has publicly admitted that there is no Wizard of Oz, and they're just a man behind the curtain, and would you please bear with us while we iron out the glitches?
Guess what? Maps is hard. Why did Nokia buy Navteq in 2008 for a whopping $8B? Why do you think Amazon recently choose to license Navteq maps from Nokia for their Kindle tablets' Maps API?
Given that Amazon makes $7 million profit a quarter and Apple makes $4M profit an hour like Gruber sneeringly likes to remind us[1], is it wrong to expect better maps from a phone that costs much more than a run of the mill cheap Android phone? What excuse is there for driving directions that direct you to drive on train tracks? [2]
[1] http://daringfireball.net/linked/2012/07/27/amzn-profit-corr...
Judging by all the cars parked on both sides of the track, there's probably a driveable surface there too. Not uncommon.
In practice the back end is really the main thing that they need to worry about. I'd argue, in fact, that the first order of business is straightening out the point of interest database, which seems to be where the majority of genuine problems are coming from. The second order of business is ensuring cartographic completeness and correctness, i.e., making sure that roads (and even the occasional town) are actually present and in the right place. Things like fuzzy terrain tiles or bad 3D meshes may be the most fun to take screen captures of for point-and-laugh purposes, but it's far more important to me that the maps application can tell me how to get to the Brooklyn Bridge than whether it can render a pretty 3D model of it.
Reporting mapping errors on a small device is painful and cumbersome, especially if you're outdoors or trying to get somewhere. Like Google, Bing or Nokia maps, can you access and report errors in the maps from a laptop or desktop? If not, this process is going to be way slower.
They know exactly that. Luckily, it's a server driven service, so over time everything can magically get better. They are going to aggressively harvest user data throughout the getting better process. Their options were: launch bad and get better as fast as possible (using millions of devices for feedback) or spend a few years doing things by hand then still releasing something subpar. Rip the bandaid off now.
In every other case HN screams "more data > clever algorithms!" -- this is their way of more data. It'll be painful at first, but it will get better quickly. It has only been a week since public public release. It has been sucking in betas for months too. None of this is new, exciting, or newsworthy. Release your burdens and get back to work.