Someone showed me OSMAnd recently while we were hiking. I installed it as soon as I got home. Great for hiking.

Then last week I used it for navigation (on a phone with no SIM card).

Absolutely. Terrible.

Worst navigation app I've seen. Told me to make a turn at an intersection that did not allow turns. Then at another intersection, it told me to "Turn left", but the display clearly showed it going straight. I'm guessing that the straight road probably is angled 1 degree or something at the intersection and the app was viewing that as a turn.

For an open source Android app for OpenStreetMap data, I like Organic Maps, and it normally works great with locally-cached maps. I've had better luck with it than with Google Maps or Apple Maps on phones.

(Though, I should mention that twice in the last year I've had Organic Maps become hopelessly confused about where I was, and where I should go. Both times, it had gotten a good GPS location, but then got confused while being out for an extended period of time, like maybe it was dead-reckoning only after that initial lock.)

This is a really interesting feedback. I've used OSMand for maybe five years, and never had issues like you're describing. I've always felt that the search was absolutely awful, so I used Google Maps for that and then put the points of interest into my map. Nevertheless, I find the display particularly dense and confusing to configure, and so I also have been using Organic Maps lately, which may provide a simplified experience that's a bit more polished.

I wonder if there was some issue with the map data in the area you were driving in that led to the issues you experienced. I've used OSMand in Belize, Mexico, California, Connecticut, New York, New Hampshire, Vermont, and Maine and had a good experience, especially with the offline maps.

On top of the OsmAnd user experience being a little rough (it can do a lot, but not gracefully) it relies on accurate OSM data underneath. So the best thing to do is at least make a Note on OSM, or edit it yourself, and mark that intersection as having a no-turns-allowed restriction.

Even Google is relying on user submissions to keep its stuff accurate these days, they just have money to pay editors and reviewers.

> Told me to make a turn at an intersection that did not allow turns.

That's an OpenStreetMap bug, the intersection likely isn't marked as not allowing turns. If you put a note (OSMAnd calls them OSM Notes) on the map someone will fix it when they can.

I get similar navigation issues with Google maps. I still use Google maps for driving because the live traffic is important to me, but other posts on here mention other apps with live traffic so I'll give them a try.