Google Maps just dropped a major update that's already rolling out to iPhone users. It's essentially their version of Detailed City Experience. Limited to an unknown number of cities in the US. You can activate it by opening Google Maps, going to your Google Account Settings, selecting Navigation, and then choosing "3D" for navigation.
I'll be testing it this afternoon. From the videos I've seen, it replicates most of what Detailed City Experience does on Apple Maps: lane markings, colored buildings, trees, elevation data, the camera moving to give you the best view, limiting information on the screen during navigation for a cleaner look and less information overload, etc. And a new thing where you can interact with Google's Gemini AI during the trip.
All of their advertising showing this off has been displayed on Apple devices, including CarPlay. They're clearly trying to win back Apple users who have switched to Apple Maps.
I think the big thing it does that is beyond DCE exclusive features is them copying natural language and showing more of the route versus “straight up” view.
Here’s what wrote on Reddit after trying it yesterday (sorry…I’m lazy)….
Okay...just did a test drive with this on CarPlay...and FYI, used both CarPlay and Android Auto previously with my Pixel phone and noticed no discernible difference between Google Maps performance or appearance on either.
Yes...they do the "turn at the next light" or "turn at the next stop sign" natural language that Apple has had for years. But a couple of problems I experienced:
* They are still hell bent for some reason on including the official "state road" or "county road" nomenclature or some other government official naming...and in some cases, only that name despite the road having a more "common" name. I don't need to hear, "Turn right onto Robert Smalls Parkway, State Road seven dash forty"...I mean, no one, and I mean no one, calls a road by the county or state designation unless that is the only designation available.
* They are still showing "paper map" road badges and not the realistic ones in actual use. I'll never understand this...Apple figured out early on, show on Maps what people see out their windshield so there is less confusion. It works!
* When on a main road and coming up to a turn at a light, Google will initially say, "turn right at the next light" and then as you get really close to the light (sometimes already in the turn lane) it will then say, "turn right at the light onto Main Street". Apple typically does the opposite where the initial direction tells you which street you will be turning onto at the next light. Mentally, this allows you to prepare to look for that street name. Really important when one wants confirmation they are making the correct turn. I know what you're thinking, why not just trust that the next light is the next light and is correct? Yeah...we all know why...it sometimes isn't.
* Because of the prior two issues (long naming, too late instructions), I generally feel like Google Maps just lags in its spoken directions compared to Apple. It just waits too long and doesn't give the info I need when I need to hear it...but that's me.
* Yes, I still feel the maps themselves look like trash...it's like I'm living in an RGB world where Apple feels like 8k. Clunky, ugly, and they still haven't figured out the draw distance despite a huge improvement by copying Apple with showing more of the route and not just the "facing up" view.
At the end of the day, it's an improvement...and improvements are good. I'll stick to Apple Maps for now and let them continue to improve their 3D created world as well as POI information.
