Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The problem with Apple's Maps app in iOS 5 and previous was the app itself, the front-end, not the backend and its data.

The fix proposed by Apple in iOS 6 is to swap out the back-end.

Google doesn't "obviously keep a better version" for their own OS, Google never made one for iOS to begin with. The front-end Application was under Apple's responsibility. All the features it lacked was Apple's own fault for not implementing them from Google's data.

Basically, they replace the only part of the app that was good : the actual Map data. That is the issue people have with it.
The front end has always been the problem with Maps, which was originally designed and never updated by Apple, not Google.

KnightWRX, it pains me to see your technically sound and logically correct posts in so many threads cast aside by blind ignorance.
 
My issue is not even as much with the amount of available data but that incorrect data is being added knowing full well that it's not correct. Take the boundary of a lake as an example. You can switch to satellite view and see that the lake continues on the other side of the road but it stops at the road on Apple's map. If you are going to draw a lake, draw it correctly or don't add to the map at all it until it is correct. It's not like Apple to do things this way. We didn't get any form of cut and paste until they felt they had perfected it.

OK, the amount of data is an issue for me too, as is losing street view but I digress.

Then maybe you should report it to apple so they can correct it.
 
Google this. There has been a lot of information. Google has a say on what features are available through it licensing. They have to negotiate the feature-set.

Ah, that also makes sense. But I don't see why voice navigation depends on Google's restrictions. It could be added with the same exact service from Google. Of course, Apple would have to make it.
 
Google Maps should've stayed as long as the Apple Maps is in beta at least. This isn't a gimmick like Siri, it has some serious uses. A shame to see a polished app get replaced by a beta.

I think most people who are using the 'it's a beta' argument have never really needed a map/navigation application extensively. Betas don't excuse removal of something as essential.

uhhh.... this isn't beta maps on finalized software... this is beta maps on beta software. Maps will NOT be in beta when iOS 6 is officially released. So this situation isn't like Siri and there is no reason Apple should keep Google Maps temporarily for the developers. Beta devices shouldn't be used as a primary. They should be used to test their apps for compatibility.
 
Maps will NOT be in beta when iOS 6 is officially released.

What makes you think this ? We're in deep Q&A by now for iOS 6, and the way Q&A works usually is that in late phases, you will actually be using your production datasets to test the application, not a limited "beta quality" dataset.

You're trying to find as many bugs in the software and the only way to be sure no data in production will trigger conditions in the software that you might not have expected is to use the actual data from production systems.

What makes you think the mapping data is not the complete, production data ? Sure, mapping data is in constant evolution, but there's no reason to believe Apple has a completely different set that's much more polished that what is currently presented to developers through iOS 6 developer previews.
 
What makes you think this ? We're in deep Q&A by now for iOS 6, and the way Q&A works usually is that in late phases, you will actually be using your production datasets to test the application, not a limited "beta quality" dataset.

You're trying to find as many bugs in the software and the only way to be sure no data in production will trigger conditions in the software that you might not have expected is to use the actual data from production systems.

What makes you think the mapping data is not the complete, production data ? Sure, mapping data is in constant evolution, but there's no reason to believe Apple has a completely different set that's much more polished that what is currently presented to developers through iOS 6 developer previews.

I never said the mapping data is not complete (I'm also not saying the opposite). But the poster I responded to was complaining about Apple replacing google maps with beta maps. I'm saying that by the time iOS 6 releases the "beta" designator will be removed. This won't be like Siri. At that time you may argue that you think Maps "feels" like a beta product, but it won't be labeled as one.
 
I never said the mapping data is not complete (I'm also not saying the opposite). But the poster I responded to was complaining about Apple replacing google maps with beta maps. I'm saying that by the time iOS 6 releases the "beta" designator will be removed. This won't be like Siri. At that time you may argue that you think Maps "feels" like a beta product, but it won't be labeled as one.

The label matters little. If indeed Apple are using there "release/production" data, there is a step backwards for users of their Maps application.
 
The label matters little. If indeed Apple are using there "release/production" data, there is a step backwards for users of their Maps application.

True. And perhaps I am being a bit too pedantic but the poster said
Google Maps should've stayed as long as the Apple Maps is in beta at least. This isn't a gimmick like Siri, it has some serious uses. A shame to see a polished app get replaced by a beta.

I think most people who are using the 'it's a beta' argument have never really needed a map/navigation application extensively. Betas don't excuse removal of something as essential.

I'm just saying that although iOS 6 is in beta now... technically google maps is not being replaced with maps that are labeled as "beta". (of course Apple could always do that, but there's no indication of that)

But I do also think that things will continue to improve dramatically over the next few months.
 
True. And perhaps I am being a bit too pedantic but the poster said

You know and I know he meant the quality of the dataset, not the label put on it.


But I do also think that things will continue to improve dramatically over the next few months.

An optimistic view. Another one is that mapping data will improve over time, but not at a rate significantly faster than Google's or Mapquest's or Bing's did. And if history is any indication, then what we are seeing now is pretty close to what we'll be seeing well into next year. Apple have a long climb ahead of them to catch up, if they can even catch up in terms of mapping data quality as competitors also keep improving.
 
Why should Flyover be US-only? There are already a few cities outside of the US available and C3 technologies had much more cities ready, when they were taken over by Apple.

Again I'll state that FlyOver seems to be a USA only feature ... this is NOT Maps but FlyOver.

Look at any city in Canada (we're just north of USA - Alaska we're East), and look at a city in 3D ... compare it to what you see demo'd at WWDC 2012 ... you'll understand.
 
There is already navigation in Google Maps for iOS, so all that Apple has to do is make it into more driver-friendly instructions (just simple rephrasing) and add a voice. It tells you "turn left at Street Avenue" and such right now.

Google's terms of service do not allow for it. Unless Apple negotiated it and decided not to use.

The most obvious answer to the question lies in the Google Maps API's terms of service itself. Google may offer most of its juicy data to developers for their third-party apps (including Apple), but it does place some restrictions on what kind of applications are allowed to be built using Google's API. And in particular, Google restricts those making apps from its APIs from offering real-time navigation or route guidance in their own apps. Here is the relevant section in the TOS:

10.2 Restrictions on the Types of Applications that You are Permitted to Build with the Maps API(s). Except as explicitly permitted in Section 8 (Licenses from Google to You) or the Maps APIs Documentation, you must not (nor may you permit anyone else to) do any of the following:

[…]

(c) No Navigation, Autonomous Vehicle Control, or Enterprise Applications. You must not use the Service or Content with any products, systems, or applications for or in connection with any of the following:

(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.
It looks like Google's terms for use of the API clearly restricts companies like Apple from offering turn-by-turn navigation in their apps. But this leaves at least one unanswered question: what if Apple and Google had worked out their own agreement that isn't necessarily subject to the TOS that are applied to everyone else?
http://arstechnica.com/apple/2012/06/ask-ars-why-did-apple-have-to-ditch-google-to-add-turn-by-turn-nav/
 
What makes you think this ? We're in deep Q&A by now for iOS 6, and the way Q&A works usually is that in late phases, you will actually be using your production datasets to test the application, not a limited "beta quality" dataset.

You're trying to find as many bugs in the software and the only way to be sure no data in production will trigger conditions in the software that you might not have expected is to use the actual data from production systems.

What makes you think the mapping data is not the complete, production data ? Sure, mapping data is in constant evolution, but there's no reason to believe Apple has a completely different set that's much more polished that what is currently presented to developers through iOS 6 developer previews.
iOS 6 beta 2 release notes explicitly said map data like satellite imagery was limited in the beta.
 
Google Maps should've stayed as long as the Apple Maps is in beta at least. This isn't a gimmick like Siri, it has some serious uses. A shame to see a polished app get replaced by a beta.

I think most people who are using the 'it's a beta' argument have never really needed a map/navigation application extensively. Betas don't excuse removal of something as essential.

Google maps has stayed when it's in beta. The beta is for app developers. Google maps should still be there in your primary device running iOS5 :p
 
iOS 6 beta 2 release notes explicitly said map data like satellite imagery was limited in the beta.

Since the notes are under NDA, we'll have to take your word for it. But as stated tons of times and if the notes that did get posted were true (someone posted the ones from the original beta), that's not what it said. The notes said satelitte imagery would improve over time, but that's no different again than all other mapping provider that do improve over time.

Some posters are overly optimistic in thinking the notes meant that the dataset was currently limited and that Apple only had to "push a switch" to load tons of great data for release. A more realistic view is that the data will improve, but not at a rate faster than the competition does and did in the past really. What we're seeing now is the best Apple can provide. Sure they are working on it, but it won't all magically be much better come release time around October.

Of course, maybe Apple did choose to do the beta on a limited dataset. Makes you question how serious they are about testing their production datasets, infrastructure and the actual application and how many bugs it could leave laying around the actual release version.
 
Since the notes are under NDA, we'll have to take your word for it. But as stated tons of times and if the notes that did get posted were true (someone posted the ones from the original beta), that's not what it said. The notes said satelitte imagery would improve over time, but that's no different again than all other mapping provider that do improve over time.

Some posters are overly optimistic in thinking the notes meant that the dataset was currently limited and that Apple only had to "push a switch" to load tons of great data for release. A more realistic view is that the data will improve, but not at a rate faster than the competition does and did in the past really. What we're seeing now is the best Apple can provide. Sure they are working on it, but it won't all magically be much better come release time around October.

Of course, maybe Apple did choose to do the beta on a limited dataset. Makes you question how serious they are about testing their production datasets, infrastructure and the actual application and how many bugs it could leave laying around the actual release version.
It didn't say that the satellite imagery would improve over time. They said that it was currently limited in the beta.

Anyone that's been using the betas can tell that the data set has changed. That's why there are "new" 3D satellite areas even though we know that C3 has had over 100 cities mapped already (but Maps will only show a few of them, even though they're the same images). The very first map beta also didn't show subway stops, even though they appear now, hospital and school data were also added to Asian countries, building/land plots are not shown right now or in the beginning, but was available in some cities during the middle of beta 2.

You don't need to stick with a pedantic definition of "beta." Siri is in beta and will still be in beta even after adding data sets comprising of multiple languages, countries, mapping ability, OpenTable and Yahoo Sports integration.
 
So many non-developers who somehow got hold of the beta are freaking out and posting embarrassing comments on internet forums.

That's how I see it.
 
Google Maps should've stayed as long as the Apple Maps is in beta at least. This isn't a gimmick like Siri, it has some serious uses. A shame to see a polished app get replaced by a beta.

I think most people who are using the 'it's a beta' argument have never really needed a map/navigation application extensively. Betas don't excuse removal of something as essential.


Isn't that exactly what Apple is doing? They haven't removed Google Maps yet and they won't remove it until the new one is out of Beta. You're not making much sense.

Something tells me you somehow got ahold of the developer iOS 6 Beta, installed it on the iPhone you use every day, and you're not a developer. And so in your mind, Apple released an unfinished Beta app and removed a "polished" app. Which is obviously wrong.
 
Last edited:
I understand that new features are withheld from older devices, but the Maps experience on my phone is now worse than it was on 5.1.1, and that's just wrong.

So the Maps experience on a released OS is better than on an unreleased Beta. Not unusual at all actually. Maybe you should wait to compare the full release of iOS 6 (which is still months away) to iOS5 if you want to make a real comparison.
 
Now I don't know about Googles Map app on android devices as I have never used it. However I have used the stock map app on iphone and ipad since 07. I was worried like most of you when I installed the beta that apples maps simply wont be ready for prime time....

Im now on beta 3 and I can't be happier with apples maps. The Yelp and Open Table integration is fantastic. yes theres no "streetview" but I hardly ever used it and the overhead view or yelp pictures of the business your looking for more then make up for it!

Turn-by-turn is glorious. Me and My gf both have indash gps units in our cars yet we find ourselves using the turn by turn on my phone because it recalculates before you even finish taking the wrong turn. searching for an address is instant rather then searching on your phone and then typing it into the car.

Overall I think everyone will be more then happy with apples maps. Recreating your own map service is a HUGE undertaking and it will take time to get every little thing people are used to from google maps right but it will get there. I also think apple devoted so much to making the map service perfect thats why its one of the only big new features to ios 6.

I miss street view but I can live without it. It was never up to date anyway. The imagery in on my street was from around 2007!

With the exception of the mission street view, I am really happy with the way Apple is handling the new mapping system. It's really sleek and and just works. I really like the Siri integration with maps too, expecially in the UK. I like asking Siri to take me places lol.
 
People who are actually arguing that Apple is ahead of Google in the mapping department are either a) dumb or b) complete apple fanboys that are kidding themselves.

The cartography in Google Maps is significantly more elegant than what is currently in Apple Maps beta.

Nobody is saying it is impossible for Apple to one day catch up to Google. But acting like it isn't a step backward at the moment is silly, when it so obviously is a step backward.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.