Great posts, thanks, guys. I will have to give OSMA a try. Dynamic, I feel your pain. I have slowly moved towards just accepting the fact that I need three different app solutions: One for the past, one for the present, and one for the future. In other words, one for planning, another for being sure exactly where I am, and one that will give me stats on my ride afterwards -- how far and how fast as well as the elevation.
What I've been doing, which sucks: Planning with Google Maps (the worst) or AllTrails or MTB project (I use the website, not the app -- better, but far from ideal), and determining where I am in remote areas with Google Maps (works well for that, particularly at critical trail junctions where a mistake could mean riding another 5 to 10 miles and running out of electrons) and Strava for archival purposes.
AllTrails and MTB project are great for figuring grade and elevation-- whether a route is actually possible for my skill level or not. For some rides, it might tell me that one segment is 27%, but that segment is only 50-100 feet and the trail is intermediate/advanced, so I figure, "Okay, I can do it, but just barely" which turned out to be right. Or I'll figure "I can do it, but I may have to walk some sections" which turned out to be accurate as well. So I think the planning part is really key-- whether you're on the trail or doing what Dynamic is doing.
Would be great if I had an app that both helped me plan a route and also told me where I was as accurately as Google Maps. Strava just didn't quite cut it for that, but maybe I was using it wrong, I have a new phone. I think what I liked about Google Maps was that I could see the satellite view, which sometimes shows trails that aren't shown on a map.