Google Maps Returns To iOS As An App

Thanks Google! :D

Not because I specifically wanted a new Google Maps app on iOS, but because I had a bet with a couple co-workers. They were both dubious that Apple would accept the app in a timely manner, so we had a pool. I chose "before the end of the year", one was "sometime in the first quarter of 2013", the other was "never" (which we declared March 31 to be the cutoff of "never".) So now I am owed two rounds of drinks.

I did test it yesterday. Some nice things (some even nicer than the Android Google Maps,) some *REALLY* wonky things. The most noticeable wonky thing was a choice of directions that every other mapping product (including other implementations of Google Maps,) didn't do. (I live in Portland, and got directions from the outskirts of Portland to the core of downtown. The start and end point were on the same side of the river. The freeway it had me take has an exit directly into downtown without crossing the river. Every other mapping product had me take that exit. The new Google Maps on iOS had me cross the river on the freeway, then take an exit on the other side of the river and take a "city street" bridge back across the river - a bridge that often opens for boat traffic during the day. The *OLD* iOS 5-and-earlier Google Maps did *NOT* have me cross the river!)

I really like Google Maps computer-generated voice for guided directions. Sounds like a continuous recording of a person, not like a computer-generated voice or a "recorded individual words pasted together" voice. But, irony of ironies, it mispronounced the name of the city in Oregon Google's datacenter is in.
 
Downloaded this already, haven't used it for navigation yet but it looks way better than Apple's Maps!
 
Maybe you have too much process running on your iPad 3?

Double tap the home button and hold down one of the bottom app and remove them all. There's a few apps out there that runs like hell on iDevices.

Nope, no background processes since it's so rarely used and turned off (I thought iOS is smooth because it barely does any multitasking). And the TF300 had a ton in the background. Maybe i should make a video the apple maps and google maps side by side and have them go through the same route.
 
Nope, no background processes since it's so rarely used and turned off (I thought iOS is smooth because it barely does any multitasking). And the TF300 had a ton in the background. Maybe i should make a video the apple maps and google maps side by side and have them go through the same route.

It's probably what kllrnohj said then. iPad 3 was the first to employ Retina Display, so it's pushing a lot of pixels for an ARM device. iPad 2 was a 1024x768 device, so it'll be smoother, and iPad 4 is simply stronger than iPad 3.
 
I still prefer Apple Maps. It's smoother and faster, has better vector rendering,

No, it doesn't. It doesn't show many details until you zoom in, which is bullshit. Never mind state highways it won't show, it will leave out lakes. It's ridiculous and unusable as a map.
 
No, it doesn't. It doesn't show many details until you zoom in, which is bullshit. Never mind state highways it won't show, it will leave out lakes. It's ridiculous and unusable as a map.

I think you misunderstood what he was saying. He doesn't care that Apple Maps sucks at being a map, it's *prettier*. The wold is too ugly for Apple, so they are showing you a better looking world instead.
 
I liked Apple's old map software that used the Google maps better then the actual Google maps app from Google you could download.
 
No, it doesn't. It doesn't show many details until you zoom in, which is bullshit. Never mind state highways it won't show, it will leave out lakes. It's ridiculous and unusable as a map.

It definitely renders better on my iPhone 5. Apple maps always only displays everything as vectors. With the new Google Maps app when I zoom in I see the rasterized image zoomed and pixelated before it refreshes and draws the map more detailed.

Also Google maps pans and zooms at around 30-40 FPS even on the extremely fast iPhone 5 where Apple Maps is always a fluid 60fps.

I've never had a problem with it not showing roads. I use it multiple times a week and I've always been able to find what I'm looking for and it always leads me there correctly. To call it ridiculous and unusable as a map is completely incorrect in my opinion since I do use it all the time and it works...

As far as not showing lakes, perhaps, but I haven't noticed. I don't ever find myself looking for a lake or driving through a lake...

I use Apple Maps for driving directions and finding places like homes, restaurants, and businesses and for that it works just as well as Google Maps in my own experience, except the apps itself is a better user experience in how it renders and how the UI works especially integrating into the OS.

It's fine if you prefer Google Maps. I'm glad they added for people who like it, but I like Apple Maps and prefer to use that. Why can't I use what I like more after trying both?
 
Back
Top