Hacker News new | ask | show | jobs
by tylerrobinson 1707 days ago
Every time I've tried Apple Maps, I run into the same problem--it doesn't seem to predict your realtime location ahead by X feet to account for your speed and delay in GPS signal. Google Maps does this. The result is that on Apple Maps, your position is "behind" where you really are at the moment, and it's harder to make the turn. Google's tradeoff is that if you miss a turn, it will momentarily show your position as if you'd made the turn correctly. Perhaps this is a matter of preference, but I am much more successful at navigating while driving using Google Maps than with Apple Maps.
2 comments

I've noticed the same thing. I do use Apple Maps in Carplay, but have learned to anticipate what's shown on-screen in-relation to where I'm actually located. Seems like it's certainly fixable, but I'm surprised it hasn't been addressed already given that two random strangers on the internet highlight that as one of the service's primary weaknesses.
Has Apple ever factored user feedback into its designs? They seem pretty dictatorial in how they approach UX.. "Apple knows best, user will adjust."

<-- typing this from a Mac, while learning how to use iPad's opaque gestures...

Possibly only Android Auto receives vehicle speed signal from a car? https://developer.android.com/reference/android/car/VehicleP...
I have never used Android or iOS car integrations. I am speaking from using GPS while driving, so I meant the app’s ability to calculate your speed based on GPS.