Indeed. I'm that idiot driving in circles around the roundabout because Google Maps gives me the turn right as I'm passing it.

Also, it's forking is completely fucked. If there are 2 right turns coming up it does not indicate which lane I should be in. In once case I had to drive 60kms, 30 kms there and back, because the interchange had 3 right exits and I chose wrong.

Now I use Google Maps to find the location and copy the coordinates into Apple Maps. Or use Waze.

Or two turns ahead if you're cycling. They don't seem to take speed into account.

The big problem is that routes used to be useful without turn-by-turn navigation - back when there were bubbles on each turn you could click on to see. Now you're stuck trying to read a long list of directions, or you use turn-by-turn and have no idea where you're going until the last second before each turn.

I agree. Apple Maps and Here maps are both a much better navigation experience now in my opinion. Google maps still has a bit of an advantage on POI, but for 98% of my uses Apple and Nokia do a better job.

This is my #1 complaint as well. "Turn right" Welp, guess I'm making a u-turn.

That seems oddly bad for being by Google and their skilled engineers. It's really just about factoring in your speed and distance... We've done this sort of thing ourselves in our apps. :/ It wasn't obvious in theory as for what parameters felt "just right", but these insights came soon enough after just a few trial runs in different speeds.

For me this is not a problem. I glance at the top left of the screen to see the direction of the next turn, left or right, then I get in the left or right lane. Also, when I miss a turn the rerouting is fast enough it's hardly a problem.

My big complaint is that Google maps announces I'm on the fastest route even when I know I'm not!