> Most people can’t tell the difference and go with the default.

Sadly, that's true. I'm a big maps' aficionado and as such I prefer the Hybrid View (satellite + roads) whenever I'm looking for an address or POI on GMaps. I've noticed that the majority of people I interact with (work colleagues, closed ones) only use GMaps on maps view, and as such they don't know how to make sense of where exactly their desired POI is, because when they zoom in on it they usually see only some colored background with some lines (i.e. roads) on the side. While when using the Hybrid view you can actually see the buildings themselves and other physical reference points (a forest, a football field, a parking lot etc), which makes it way more easier for you when you actually want to get to said POI.

As such, I fully believe that for these types of people switching Apple Maps in place of GMaps would make no difference at all, it's just switching a blob of colored backgrounds and lines with another blob of colored backgrounds and lines, while GMaps' preeminence, IMHO, is in its exceptional and unique satellite views quality.

This kills me. I uninstalled Apple maps and I have to manually copy locations into Google Maps from the mail app. Clicking location links prompts me to reinstall Apple Maps. Obviously a very intentional decision.

When I go to google.com with a browser other than Chrome, I see a pop-up "Switch to Chrome, a smarter browser. Google recommends using Chrome. Try it? [Yes]" Each company leverages what they have to try to push you further into their ecosystem (or as Bruce Schneier would say, further indentured to that feudal lord).

There's a pretty significant difference though. One is a message on a company's homepage, the other is a limitation baked into the OS.

At least on Android, clicking a location link will allow you to open it in any installed application that's registered to handle it.

I prefer usability (UX) over content, I used to switch to other maps when I had issues with data, but there hasn't been the need to in a very long time. Default is great especially if the UX is better. Google is ok, but Apple Maps UI is the best. I still use Waze from time to time though.

I find Apple Maps annoyingly slow in calculating routes and responding to my input. Google Maps worked alright for me, but I switched to Waze a couple months ago and can't go back anymore.

Waze is superior in so many ways. It knows (most) contruction sites/road closures (there are many where I live), Waze tells me about speed traps and accidents. Maybe not the best UI, but I definitely get the best results. And I enjoy submitting Road closures etc myself - hoping that I am helping others get where they want faster/without unexpected issues. It's not perfect, but it has definitely saved me a lot of time.

IMO, Waze is hit or miss, but fun. If you're doing a multi-car road trip the little messaging/beep features and stuff are fun. It overweights traffic and underweights stop signs and lights. It's great for inter-city travel, especially if you're a little familiar with the road.

But it's subject to flights of fancy similar to MapQuest circa 2002 where you find yourself taking some strange back road to save little or no travel time.

It does not give traffic enough weight for my commute. Waze is consistently too optimistic in travel time by 10-15 minutes (25% of my commute if I hit rush-hour).

With no traffic, it's spot on. I feel like it doesn't account for traffic that develops during the commute. Given the length of my travel, the roads may be clear when I start, but very congested before I finish.

I’m suprised that info isn't built into Google Maps since Google owns Waze.

As far as I know, they are using some of the Waze data like current traffic situation to calculate travel time - my guess is that they want to keep Google Maps "uncluttered", because in comparison Waze appears pretty cluttered.

On a road trip I took in May, Waze couldn't seem to stay connected on either of two iPhones. Google Maps had no such issues. I'm not sure why that would be allowed to happen, given that Google owns Waze anyway.

Funny you mention that - this has happened a handful of times lately and I am not sure why. The network is completely lost and I have to quit and reopen the app on my iPhone for it to work again. I assumed it was due to my carriers (o2 germany) general unreliability..

Waze is much more of a CPU and bandwidth hog, it's quite possible your phone is just overheating and throttling especially if it is also charging st the same time and getting hit by sunlight.

Ha! Thanks, quite likely as i notice it overheating frequently when navigating and never connected it to waze. Will keep an eye on it and compare to Google Maps. Would be reason enough for me to switch backt ..

Depends where you live. In London, Google Maps makes tube stations obvious with a big London Underground logo. Apple Maps gives them a tiny purple icon that gets lost in the noise.

I have an awful time over the compass on Google Maps and Apple Maps on both my iPhone. I seriously don't know why. It is so adept at pointing in the exact opposite direction that I do not trust the compass anymore.

Is this just a Maps thing, or does the Compass app also give incorrect results?

It's difficult for me to test the Compass but it is very apparent on both Apple and Google maps.

There's a built-in Compass app that you could use…

A lot of people just know Google Maps as "Maps" anyway and don't understand that it's not all the same.