* Rendering is faster on Apple Maps

* Apple Maps caches a much larger area offline, while Google Maps is basically useless without a network connection

* Apple Maps integration in iOS apps is better than embedding Google Maps, which is very obvious if you compare 3rd party public transit apps that use Apple Maps to Google transit directions.

Not saying Apple Maps is nearly as good as Google Maps (because it isn't), but 'totally annihilates Apple Maps in every way' is simply not true.

Google Maps for Android has the possibility of caching e.g. a whole city offline, which is great for travelling (since we haven't solved roaming yet). It might be a Labs feature. The iOS client has been lagging so bad, I figured they would have fixed a lot in the new version.

I've been getting around the "no network" issue by using the Garmin app anyways.

Unfortunately, the better integration of Apple's app is something I have not figured a work around. Other than getting an Android phone, I mean.

Once you get past the onerous task of searching for your destination, i found Apple Maps to be much better

When it's not shoving down a Google account login down your throat, places where Google maps is better (exactly where you'd expect it be)

1 - In POI and searching. However in the limited searches i did (in the Bay area so i guess the Apple Maps critics immediately discount that) both did the same. Given the widely documented inaccuracies and just downright lack of data in the rest of the world, this is probably orders of magnitude better.

2 - Public transit - This is obviously a no-contest. Apple Maps just doesn't have it.

3 - map data - This is probably the same as POIs.

>Navigation is great, so much better than Siri's dreadful voice, easy to navigate from A>B with a tap of your destination.

Navigation isn't great on Apple maps because of Siri's "dreadful voice" ?

>Great release - welcome back

I agree but the whole annahilation bit a quite hyperbolic.

Isn't the purpose of maps to find your destination?

Can you elaborate on what you find much better in Apple Maps? It probably has better typography/layout design, but other than that?

True. Google has everyone beat in finding things. These advantages are apparent in the Google maps website itself. Once found though Apple Maps is smoother, more responsive and, in general pleasing to look at (although the last part is subjective and personal preference and many people will find the Google Maps better maybe).

Map data deficiences in Apple maps are well documented at this point and map data is the single most important thing about a map. Google Maps is superior ( and i'm guessing outside of the bay area/the US, orders of magnitude better ).

I did miss out on another big advantage of Google Maps - Street view (which i guess is part of the data but it is still unique to Google Maps)

The original comment waxed lyrical about how it "annahilates" Apple Maps in "every which way" which didn't gel with my experience. it's better in the parts it is expected to be. I wonder if anybody, let alone Apple, will ever be able to come even close to Google Maps for sheer data.

Some people do not notice the difference between 20fps and 60fps. But there's more to that than responsiveness. In comparing the two apps: How quickly do searches happen? When clicking on a result, how quickly does the info card come out? How long does it take to draw the map when you pan to a distant part of the map?

My findings: For searching. Google Maps has a much better autocomplete all round. Faster, more readable and elegant. Once you have selected an entry then Apple Maps jumps straight there. Google Maps does a handy move animation showing me the relative location, although it slows things down a litte. I LOVE this feature. For panning. Apple Maps is equivalent to Google Maps. Apple Maps has a fade in transition for loaded tiles which is a nice touch. For POIs. Apple Maps is showing me a few POIs - often in the wrong place. Google Maps is showing me all key POIs in exactly the right place. Google Maps is the first mapping product to get my home address correct (TomTom, Navigon, Garmin, Apple).

For UI. Google Maps has a nicer UI. Apple Maps requires you to click on a small button which goes to a separate screen with more options. I really like the sidebar that Google implemented.

Overall. Google Maps has much better street data and nicer UI. Apple Maps had a smooth UI, showed POIs in the wrong spot here in Australia.

I think the competition is great. Looking forward to seeing if Apple can lift their socks on the next incarnation of Maps - they have a LONG way to go.

And which POIs are inaccurate exactly ?

For searching. Google Maps has a much better autocomplete all round. Faster, more readable and elegant. Once you have selected an entry then Apple Maps jumps straight there. Google Maps does this pointless move animation making it about 2-3x slower.

For panning. Apple Maps is definitely smoother and has a higher frame rate. Especially if you have traffic/hybrid mode enable in which case even on my iPhone 5 Google Maps is lagging really badly. The biggest difference is that Apple Maps shows you a checkerboard for missing tiles whilst Google Maps has a blurred image. Apple Maps also has a fade in transition for loaded tiles which is a nice touch.

For POIs. Apple Maps is showing me lots of restaurants, bars etc. Google Maps is showing me nothing. This is in both Sydney and Melbourne.

For UI. Google Maps has a much better UI with info card. Apple Maps requires you to click on a small button which goes to a separate screen with more options. I really hate the sidebar that Google implemented. It is far too difficult to click with the tiny button especially one handed. And it isn't that intuitive that the street view picture is actually a button.

Overall. Google Maps has much better street data. Apple Maps had a much smoother UI, actually showed POIs here in Australia and the inbuilt 3D view is better implemented. The 2.0 versions of both apps should be real nice.

The road data is good buy very old. Roads that are listed have has buildings on them for years, dead ends aren't, just general mapping issues there. For some reason they've listed half the tram stops as train stations too, which doesn't really help.

I want to love them. The vector map tiles are silky smooth an very easy to navigate. The app is well thought out and easy to use. I just wish they'd used better sources for their data.

On the contrary, iOS 5 maps (Google bitmap tiles) and iOS 6 maps (Apple vectors), were generally comparable in Rome during the month of September. Neither was ideal, and cross referencing both helped.

For driving, Navigon Europe beat them both quite handily.

What's more, during my visit to Italy, the iOS 6 maps improved several times. As one example, in early September the areas between streets were a single background color, but by the time I left, they showed shaded buildings for every block.

By now, the historic center is rendered in astonishing "3D buildings" mode, making the hybrid view the easiest way to orient yourself among the maze of twisty streets and fantastic landmarks. Google Earth is cool, but doesn't look like the real city in miniature, and has severe memory problems showing Rome when zoomed close enough for rectangular instead of triangular buildings. I'm not going to say Apple's view "annihilates" Google Earth, but it feels like a completely new generation of technology by comparison.

Using the new Google Maps, asking for transit directions in Rome today says none are available for the region.

Doing the same in Apple maps offers to launch Navigon Europe on my phone which has "Urban Guidance" for Rome, but also gives me a list of local data specialist apps such as In Arrivo! HD (which claims to have real time bus positions).

All this said, when browsing Rome the new Google Maps app is significantly more speedy than the iOS 5 version, though it suffers from the early Apple Maps problem of having no data for roads (much less POIs) when zoomed out even a little, and when zoomed in a bit, is very challenging to read at a glance and still misses most points of interest.

> Google has everyone beat in finding things.

In the Trastevere restaurant neighborhood, Apple's data shows 10 restaurants for every 1 on Google Maps, any of which can be tapped to see a photo of the building and read reviews on Yelp. Google Maps, if zoomed in far enough, eventually shows you the POI, and can be tapped for a street view panorama rather than the actual storefront.

The wildly popular local seafood hangout "Fish Market"[1] shows up on Apple Maps with 3.5 stars and 5 reviews, but doesn't show up at all on Google Maps. Searching for it sends you to the other side of the Tiber, to an actual fish market.

1. http://www.tripadvisor.com/Restaurant_Review-g187791-d334907...

My point isn't that Apple Maps data is better, but that to a local who is looking for differences, either product can be shown to come up short. This suggests neither is "orders of magnitude" (presumably meaning at least 100x) better than the other, even when comparing this new offering rather than the iOS 5 version.

I hope they'll integrate the local iOS address book with the next version.

- Type Pub name, "Not Found"

- Type Postcode, It points to completely the wrong street

- Type street name/number, it thinks I mean some street in America (Map screen was focused on london)

I'm not sure people understood how much they took the original gmaps for granted until Apple released their own.

He means that the actual searching (ie the querying to find) is not well implemented.

Besides that, no, the purposes of a Map app is much more involved: show you turn by turn instructions, public transit routes, bookmarks, etc...

How is it shoving a Google account down your throat? It took me a minute to find where to log into my Google account so that I could retrieve my saved Maps places.

How do you contrast this with Apple Maps, which transparently uses an iCloud account on the backend?

Do you lay the blame on Google? Or Apple, for not having system-wide account services for Google (as they do with Facebook and Twitter).

Since Apple Maps works perfectly fine for my area ( yes, i'm aware there's a world outside the Bay Area where Apple Maps is horrible), the constant nag for a login is enough to for me to stop using it. It is an awesome app though.

  > Wow. New GMaps totally annihilates Apple Maps in every
  > which way.

It turns out that getting directions via transit works as expected. I'm not even sure what the transit link when you swipe left is supposed to show. So it's a weak ui in that respect, but the app gives me what I was missing.

My observation is that it (1) turns off some of the excessive highlighting of highways and other roads (which for some reason is done by default even in very transit-oriented cities), and (2) it turns on highlighting of "rapid transit" lines.

Unfortunately the definition of "rapid transit" used for this function is sometimes very poorly thought out.

For instance, Tokyo has a massive rail system that covers the entire metropolitan area with a fairly consistent level of service. However Google maps only considers the city-center subways—which form about 25% of the entire system—to be "rapid transit", although from a user's point of view there's very little difference between subways and most other rail lines in Tokyo (they generally use similar scheduling, rolling stock, stations, and even station spacing in many cases). So enabling the transit option in Tokyo highlights subways, but it actually de-emphasizes many other (essentially equivalent) rail lines!

The only thing I can think of is that the design of this feature was based on the particular city (e.g. NYC), and then sort of slapped onto other locations without a whole lot of actual thought... :(

Maybe they just roll a pair of dice...?

If you're into 3D satellite views, this is available in the Google Earth for iOS app. Google launched the 3D flyover stuff in that app a couple of months before Apple released iOS 6, so it's been around for a while.

If you have Google Earth already installed, then you can jump directly to that app in the swipe-left menu of the new Google Maps app (and it will even jump to where you were looking in the Google Maps app, so it's pretty seamless transition).

Hopefully they will enable an in-app mode in the next version.

Personal experience report on an iPhone 4: the app is laggy as hell with one to two seconds of delay when dragging. You have to actively combat inertia to navigate around, and minimal movement occasionally sent me overshooting by multiple screenfuls. Also, it keeps wanting to turn north around on the slightest twist when zooming, which is even harder to handle due to lag.

> Someone else mentioned that it's simply GMaps in a UIWebView - no chance for that.

That's not how it looks, but that's exactly how it feels. Well, that's also how it looks on the login screen given the overflowing sign-in form. The drag lag on the map feels like the typical JS-overriden scrolling. I'd really not be surprised if it is a UIWebView and a properly designed web app (not web site backportedly shoved in as an app).

On this hardware, Apple Maps has a clear victory on the performance and interaction front.

I would agree that it gives the app an unpolished feel, that and the sign in nagging. Otherwise the functionality is great.

There are some places it's fine. Other places it's problematical. Other places it's a complete disaster.

The last two categories seem to outweigh the first for me. In the UK especially where basic things like searching for local train stations (we actually use public transport quite a bit here ;-) seem to fail completely in large chunks of the country.

Since my experience of Google Maps on the iPhone until the switch over was that - as long as I could get GPS and an internet connection - 100% fine the Apple maps app is a complete fail for me. I can understand that there might be reasons for it being necessary from the business perspective - but for me personally it now means I have had to have three map apps on my home screen to get around rather than just one.

I'm hoping I can switch back to Google Maps to have one thing that works.

I could rely on it totally.

I'm not going to say I can't see what the fuss has been about as I've seen enough examples to know that there are real and significant problems, but I can say where I live (west of Scotland) for my use cases (basic searching and navigation) I've not had anything to complain about.

Q: "Where's Dulles Airport?"

A: I couldn't find any places matching 'Dulles International Airport'.

Honestly, if anyone has a voice search that will find it, let me know.

I'm not the grand-parent poster, and no Apple fanboy ... but I am inclined to agree with his sentiment.

Also, the Google Maps app for iOS hadn't been out for more than an hour and already users were touting how it was flat out better without even having used the damn thing out in the real world. How is that being an Apple shill? If anything, I'm saying: reserve your judgement until after you've used it for a week in the meat space, and don't claim it "annihilates" Apple Maps at 1 am in your dinosaur pajamas after it has been out for only an hour.

I'd be surprised if they polished anything, considering you can't exactly reuse Java code when writing an Obj-C app. They just have a lot of very talented engineers and actually cared about making it nice.

Why does it say "preview", when it actually means "start navigating"?