The OP's point is that this feels a lot like Antennagate 2010, where a large number of non-Apple users latched onto the fact that there was something wrong with Apple products, and complained louder than the actual Apple users. At this point, we can call all the evidence anecdotal until we see some hard numbers on how much map data is actually incorrect, and what actual percentage of the population is affected (I'm not holding my breath for that data, though).
I agree, though, that Apple rushed in prematurely with a new version of Maps -- either they screwed up big time engineering/management wise, or their hand was forced business-wise (I'm leaning towards the latter).
So putting the "outrage" aside for a moment, how well do maps work on your phone, and did you notice any problems so far?
To me, Google's tone at their pre-WWDC Maps event (and the effort they made to demonstrate things on iOS devices) doesn't seem consistent with the hypothesis that they decided to force Apple's hand.
> The OP's point is that this feels a lot like Antennagate 2010, where a large number of non-Apple users latched onto the fact that there was something wrong with Apple products, and complained louder than the actual Apple users.
The difference here is that there actually was something wrong with the iPhone rather than people having a preference to using Google Maps. Apple is banking on turn-by-turn keeping enough people at by until they're able to squash the shortcomings.
I agree, though, that Apple rushed in prematurely with a new version of Maps -- either they screwed up big time engineering/management wise, or their hand was forced business-wise (I'm leaning towards the latter).
So putting the "outrage" aside for a moment, how well do maps work on your phone, and did you notice any problems so far?