That makes me wonder if original turn-by-turn restrictions were Google's idea or a requirement of Google's existing contracts. If so, it's obvious Google decided to continue those restrictions for their own reasons and so history has repeated itself.
This is from Google's Maps/Earth API TOS:
10.2 (c) No Navigation, Autonomous Vehicle Control, or Enterprise Applications:
(i) real time navigation or route guidance, including but not limited to turn-by-turn route guidance that is synchronized to the position of a user's sensor-enabled device.
- https://developers.google.com/maps/terms
As far as I know, that clause has always been in the TOS (I looked into the licensing in 2010 and it definitely was in there then).
I don't need or care about 3D view or vector maps or turn-by-turn navigation (although I see how the last one could be useful for a lot of users). I, like most city dwellers, need directions that take public transit into account. I can't believe Apple released an "upgrade" which downgrades such critical functionality.
There are few times that I wish I could have been a fly on the wall in Cupertino. This is one time I wish I could have. The discussions and reasoning that went into this decision must have been fascinating because there is no way Apple was thinking, "Maybe they just won't notice". There were undoubtably a lot of tactical and strategic decisions that went into what we see, and being party to that would have given a lot of insight into Apple as a company.
2) But even assuming you're one if the lucky few for whom Google provided public transport information, you can still use Google maps from the browser. You can even add an icon in Springboard for it, giving you full access to google itineraries. The only thing that has really been lost is street view.
The beauty of Google's Transit compared to apps maintained by the transit companies themselves is that it supports cross-company travel.
Hoever, planning e.g. a trip from London to Paris, with local transit on both sides, may be difficult.
http://www.google.com/intl/en/landing/transit/
Millions of people relied on transit directions from their iPhone every day.
[1] Ok so generally reciprocity is mutual benefit but I couldn't resist the alliteration.
How about saying - "Dear iPhone users, your iOS map experience might downgrade little bit in certain cities of the world after upgrading to iOS6, because Google chose not share their Map data with us. We apologize for incovenience but we are working hard to ensure our own Map coverage improves worldwide "
As others have said without knowing the Google/Apple maps contract details we don't know if Apple could have given customers the choice.
The problem, however, is that this article assumes something to be unequivocally true even though we do not know whether it is: That Apple decided to build their own maps in order to hurt Google.
It takes two to play. Both Apple and Google have to agree that Apple gets to use Google’s data – and on the conditions. That we know nothing about. We do know, however, that the old Maps app was perpetually stuck in 2007 while Android phones gained 3D views and (much more important) vector maps and turn by turn navigation. If Google refused to give that to Apple it’s perfectly understandable that Apple goes looking for alternatives.
I’m not saying that’s the case. It could really be that Apple’s intention here was to hurt Google – but we cannot, as this article does, just assume that to be true. (To quote: “We all know the reason why Apple is doing these things. They’re more focused now on hurting Google than thrilling users, just like they were with Microsoft in the 90s.” – no, we do most certainly not all know that that’s the case.)