If I've missed it, sorry - but I see no threads directly comparing these two common Android navigation apps. I see some comparisons within Osmand and Locus specific threads, but that's a pain to try and navigate through. I see value in keeping the comparisons between them in one place, but hey...if I'm alone in that regard, I'm content to watch this thread sink into digital oblivion. I'm curious if those more knowledgeable with both apps find the following initial impressions accurate. Currently, I'm evaluating both - and I've a pretty ideal location and test case living on the Olympic Peninsula in Washington. I'm using GripTwister's Olympic Loop Tour as a test case, being able to hit it up right in my back yard. I'm tech-savvy, but admittedly somewhat naive with both apps having only used them for a couple weeks - but these are my observations so far. Please don't be shy about pointing out errors or other advantages/disadvantages you might be aware of, but I'm hopeful this thread will help others decide between the two. To cut to the chase - I find Osmand lacking for adventure riding. However, with development taking place at such a rapid pace - perhaps the shortcomings I've observed compared to Locus are temporary. Or, perhaps they don't even exist and more experienced Osmand users will advise. Regardless, I think it is safe to say Locus is far more complex and has a significantly higher learning curve. That complexity though, makes for the flexibility that leads me to stick with it currently. All of the following Locus vs. Osmand examples I find critical for adventure riding. - Custom and easily configurable screens via the Locus Dashboard editor. For me, this one alone makes Locus the clear winner over Osmand at this point in time for offroad riding. I find a critical component in following an offroad track is being able to easily see upcoming waypoints - and the tiny waypoint text on a map just doesn't cut it. Be it aging eyes, the location of the phone down on the handlebars or both - I want to see data that's important to me in big, bold letters. With Locus, I've a custom overlay on my current setup that shows the next waypoint in HUGE text at the bottom. Additionally, Locus allows you to configure screen data to come and go with a simple double-tap - allowing a full screen map with minimal info, or gobs of data based on your desired overlay. - Ability to accurately and completely import GPX data. Osmand has given me issues with more complicated imports. For example, in the case of the GripTwister GPS tour mentioned above - it doesn't import the routes contained within the all-inclusive GPX file. It imports tracks and waypoints just fine, and if you manually edit out the routes from the GPX file and import them individually - that works too. However, Locus (or CalTopo, or other tools I've tried) import everything without need for such hoop jumping. - Custom waypoint icons. How Osmand got this far along without them is a mystery to me, but I find these mandatory for custom routes/tracks. With Osmand, I've no idea if an upcoming waypoint is a turn indicator or some kind of point of interest without stopping, selecting the waypoint and reading the details. With Locus - the imported GPX file contains extended info for the waypoints via the <sym> tag, so icons are associated with things like campgrounds, fuel locations, etc. There's much more, but this is already turning into a mini-novel. I'll hold off and see if there's interest in this comparison thread before carrying on more.