Hacker News Reader

Comment by nowherecat | Hacker News Reader

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.

View on HN

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 ..

Reply on news.ycombinator.com