Quote:
Originally Posted by
Quadra 610 
But they've *already* had all that time in development.
Why are we being asked to wait for something we already had?
Apple could have at least made their Map app as an App Store offering, with a *Beta* disclaimer somewhere, until it was ready. OR NOT RELEASE IT AT ALL UNTIL IT WAS PERFECT.
The way these datasets work, they actually need to be corrected by the end user. That's why there is a "Report a Problem" button behind the map. Unfortunately, Google's map data is only good because we've had 6 years or so of people sending in complaints about the data and Google fixing the data.
This is the main problem I have about this article and the others I've read. They focus on funny data problems like the phantom airport in the article above, when those are just errors in the dataset that are easily corrected.
Personally, I am seriously disappointed with the app and think it's an absolute POS so far, but not because of data errors.
It's a POS because of the missing functionality (Streetview for example), which will *never* be replaced.
It's a POS because of it's insane OVER-focus on cars and turn by turn.
It's a POS because you have to decide which type of directions (car/walk/bus) you want *before* you actually search for a route.
It's a POS because once you have routed, you cannot then go back and see what it would be like if you took a car or bus instead.
It's a POS because they didn't even *try* to make it work properly outside of the USA
It's a POS because lots of cities with freely available, open-source, 3D data are not 3D in the app
But the thing everyone is focussing on is the data errors instead. :-/
The data errors make good copy but people should be focussing on what a steaming pile of poop the app itself is, not the data.