Besides the brand? I don’t drive but I know plenty of people who use Waze as the “car gps” but gMaps as the “search engine for places”.
Even if it’s just a GUI, different apps get you different experiences, and if you succeed it’s a bigger % of phone usage. People who mentally treat location searching and navigation as separate tasks (worthy of separate apps) are at risk of leaving for a competitor. So build two tools specific to each use case. It’s the Unix way.
I don’t know if this is the case, but it’s likely there is some left over legal issues to wrt user data.
Yeah Waze is just such a different experience for me. I haven't noticed the "riskier driving" mentioned by others in this thread but in Waze I find the voices friendlier in the languages I speak, giving instructions more often timing them better. Also you have the aspect of seeing other Waze users on the road, giving the app a cozier familiar feeling in a way. The ads suck though but oh well
Use case - Road warrior who spends around 3 months a year traveling in various areas of the US, 50/50 urban areas vs rural or very small towns.
I find the Waze experience on Carplay to be far superior to Gmaps. I prefer how it provides access to the key features like reporting/voice prompt, the size/position/color how things are displayed, etc. The level of detail (surrounding streets and landmarks) is more useful on Waze.
My experience has been that Waze seems to have better traffic prediction and avoidance in the areas I use it. Just last night I was following a cow orker from the plant we were working at to a restaurant about 30 mins away. We were right behind each other when my Waze suggested taking the exit and following a different route than my friend. I arrived at the restaurant a good 5 minutes before him, I asked, and he was using gmaps.
From my experience Waze always optimized for getting to the destination as fast as possible, which I really liked. Other navigations like to keep instructions simple and keep you on the large roads, Waze has no problem routing you through 10 extra instructions to save a minute.
Disclaimer: I haven't used Waze in years so this might have changed.
I'm not sure it is a compelling justification to have two whole separate apps but Waze's pitch seems to be "we'll send you down all the little residential streets to save a minute or two" and Google Maps is more conventional.
> What’s the benefit of Waze being a separate app at this point besides the brand name? Why not just fold it into the main Maps app?
There are differences in my region which make me think that the apps have different mapping and routing engines.
Turn by turn dirrections and road condition information are much more accurate in Waze. There's a larger Waze local community that helps keep maps up to date.
We do use Google Maps, but mostly as a Yellow Pages substitute or for checking business opening time.
Then Google should add those features to its main product. It seems idiotic for Google to maintain two maps products like this--and has been for years.
I'll give you two extremes:
- a grandma who is not that comfortable driving, not that comfortable with technology, etc. and is never in a rush.
- a urban taxi driver whose livelihood depends on hustling to destinations as quickly as possible, even through trickier driving scenarios.
If I told you one uses Maps and one uses Waze, could you guess which one is likely which? That's the two use cases.
On a technical level I agree this can be an option. On a product positioning level that's not how it works in general. You buy/chose a product based on it's overall feel.
There's a reason minivans don't come with an option for supercharged v12 engines. In theory you can say that people can just "not chose that option" but there's something deeper about how the product is positioned in the market there.
Just like you wouldn't expect an option on a minivan for drag racing mode, you don't expect an option for crazy routing on a mainstream app. Grandma can activated it by accident and cause huge traffic trying to make some impossible left turn. It's not worth it.
Or rather, the group of people in Google who are in charge of this product are reaching the conclusion that it's not the same thing. I don't know the details of their thinking,I can just come up with my own thinking for why it could make sense.
Oh I can tell you pretty much exactly their thinking. If Google folds the functions of their products into another product/team, a number of them are going to have to find a new role. I think you'll be hard put to find a product manager or development team that goes "Eh, we should just kill my product. The competing product is better for most people."
Funny enough as an eng manager and later a product manager, I've argued (and won, once) that my product shouldn't exist. I got promoted for that :)
But more to the point, devs and PMs have managers and at some point, some manager is "paying" for both products and must be weighing the pros and cons of consolidation vs separation.
Waze used to route you on the fastest route regardless of how private or rich a neighborhood is. Don't know if that's the still the case, but Google maps definitely doesn't give you the absolute fastest route, but rather the fastest route that takes major roads.
Could be related to Braess's paradox? In this case "adding lanes" would be "increased routing"
> [The] idea was that if each driver is making the optimal self-interested decision as to which route is quickest, a shortcut could be chosen too often for drivers to have the shortest travel times possible.
Personally I'd rather not go through neighborhoods for just a tiny micro-optimization because of how much more "work/attention" is required given the increased pedestrian traffic.
Could this be simply a case of "the needs of the many outweigh the needs of a few"?.
For example I live near a busy road during "rush hour" in the morning and evenings. A few mins up the road from me 2 major roads intersect which causes more hassle during these peak times. Now If you are travelling West to East to wish to turn right at the intersection to continue your journey south its quicker during those times to cut though my neighborhood (and same in the other direction) and cut out the queues leading up to the intersection. However my neighborhood's roads are not designed for that much traffic to flow though them (cars parked in the street narrowing the roads and reducing visablity of pedestrians esp kids playing outside).
The handful of locals that travel though the neighborhood to get home (live one side but enter the other) are fine however if Google Maps routed everyone wishing to make that turn though the neighborhood it would make the neighborhoods roads much less friendly to the pedestrians of the neighborhood esp at times kids are going to school or are back home from school and playing outside.
Keeping the through traffic to the major roads keeps everyone safer, and actually faster overall because the major roads aren't littered with cards parked in the road creating bottlenecks.
Much like how the london underground lies to travellers and routes them around long detours during busy periods to help prevent a crush if they all went the shortest & fastest route possible - https://youtu.be/IrHRQSm6LIs?t=57
Not really my experience. Seems to depend what "mood" Google Maps is in. I've definitely had it take me on circuitous routes even with recent snow which almost always makes the circuitous routes worse. If you somewhat know the area you can of course usually override.
In France, Waze is essentially a speed trap detector, I am sure it is the biggest use case, more than navigation. Maps don't do that.
The thing is: what Waze does is borderline illegal, and it is regularly updated to still do its thing without getting struck down. Google Maps is "cleaner", and therefore much worse at detecting speed traps. I guess the questionable legality is a good reason for keeping these apps separate.
Many people still use Waze for getting live traffic updates on a roadtrip (object on road, police speed trap ahead). I don't think those features were fully incorporated into Maps.
> Many people still use Waze for getting live traffic updates on a roadtrip (object on road, police speed trap ahead).
Once I showed my father-in-law the "police reported ahead" and "hazard reported ahead" features he was sold. He now demands Waze on every road trip and he's not especially tech-savvy. Google doesn't supply this same data.
I can confirm that it is 100% not the case on iOS. There is not a way to report these things on the CarPlay app at all, and only very occasionally will there be a "speed trap" alert on Google Maps.
That's exclusively a "not implemented in CarPlay" thing, the feature is very obviously supported in iOS; it even has its own "bubble" in the main UX while navigating.
It's crowdsourced, so it depends on another Waze user having spotted them and put a report in the app, so the usefulness his highly dependent on how many other Waze users are in the area.
Never understood this either. Even if they need to be separate apps on user devices for brand / user / other reasons, seems like they should be light skins on top of the same core app. Amazing it took 10 years to combine the teams.
gMaps has really bad direction detection imo, Waze is fantastic. Every time I use gMaps it gets very confused about where I’m facing and will randomly assume I’m turning left or right, I’ve seen this happen on both iOS and android, Samsung, LG, and Pixel, since gMaps started having turn by turn directions. Idk what gMaps is doing wrong but it’s really annoying.
Having separate apps is better for users. I personally find Waze way better than maps for driving (it's still crap mind) - whatever your opinion about their relationship merits, consolidation will remove choice.
It doesn't surprise me that Google's doing it, what's the point in having a monopoly if you can't use it to your advantage. It's not good for users though.
What’s the benefit of Waze being a separate app at this point besides the brand name? Why not just fold it into the main Maps app?