In other news, the iPhone 5 has been jailbroken.
I instantly regretted updating mine to 6 on Thursday night, the google map showed my location at home precisely and all versions of the map worked, whereas with the new "apple" maps my house was in the midst of a grey/brown field with no definition, this is in an urban area as well :/
Honest to god I think iOS6 is the absolute worst thing apple have done to the iPhone in the short time that I have had one (7 months into a 4S here), on top of maps instantly becoming crap, my battery life has now started tanking on the phone, last night when I got home from work, my battery was on 7%, averages around 40-50% normally % when I get home on any normal day and yesterday in work was fairly quiet compared to most days also.
We berate M$ for some of the stuff they do, but I just cant see how apple would release something that's clearly untested as a whole, especially if you buy into their whole "Quality User Experience" ethos.
Apple had over a year left on Google Maps contract, Google scrambling to build iOS app « The Verge
Apple's decision to ship its own mapping system in the iPhone 5 and iOS 6 was made over a year before the company's agreement to use Google Maps expired, according to two independent sources familiar with the matter. The decision, made sometime before Apple's WWDC event in June, sent Google scrambling to develop an iOS Google Maps app — an app which both sources say is still incomplete and currently not scheduled to ship for several months.
Then why is the google app (which was leaked onto Cydia) ready to go and working better than apple maps? lol
On the Timing of Apple’s Map Switch
If you think about it, it makes strategic sense that, if Apple were going to break out on its own for mapping data, they would do so while there was significant time remaining on the maps license with Google. iOS is on a more or less annual development schedule. iOS 6 just arrived last week. iOS 7 is probably not coming until a year from now, and even if it’s on a more aggressive schedule, Apple would surely seek the luxury of having the option to wait until a year from now to ship it.
An all-new maps back-end is the sort of feature that Apple would only want to ship in a major new OS release. Technically, they could roll such a thing out in a 6.1 or 6.2 update, but major changes — and I think everybody can agree this has been a major change, for users and app developers alike — should be delivered only in major new OS updates.
But if the old agreement between Apple and Google expired in the first half of 2013 (which, again, my own sources familiar with the matter agree to be the case), that means the deal was set to expire halfway through the expected year-long life cycle for iOS 6. If Apple had stuck with Google Maps for another year they would have been forced to renegotiate with Google in a situation where both sides at the table would know that Apple either (a) had to agree to whatever terms Google demanded to extend the deal; or (b) would be forced to swap the mapping back-end of iOS 6 midway through its development cycle.1 However tumultuous a change this has been in iOS 6.0, it would have proven more tumultuous and controversial if Apple had been forced by failed contract negotiations to squeeze it into a 6.1 or 6.2 update come May. And, that would have forced Apple to devote significant engineering resources for an iOS 6 update that could otherwise have been applied to iOS 7. Big changes come in the major release; bug fixes, security updates, and minor improvements come in post-major-release .x updates.
Whatever chance there was for Apple and Google to agree to a longer-term deal for iOS to continue using Google Maps, the effective deadline for Apple to make that decision was earlier this year, not next year when the existing deal expired. Apple wasn’t going to wait to negotiate until their backs were to the wall with the currently-shipping version of iOS reliant on Google Maps when the old deal expired.