Offline navigation, turn by turn and the ability to actually run it on my phone are top features. The rest are loosely structured by how nice to have i think they would be but again they are nice to haves.

First two are what I need to make it usable for me. Next four will make me happy to use it (I won't feel I'm sacrificing on experience etc. for the sake of philosophy). Active development is nice to have, but if an app already has the main features we need then a slightly less actively developed one is also fine. I put "easy to install" in the middle because at least right now I think if people are running Phosh they will probably have the patience to work a bit more to install the app.

It's a bit hard to order these... I put the no API keys or accounts at the bottom because I consider that it should be included in the "easy to use part". In addition, I would appreciate the ability (like in the android version of organic map) to log in with an OSM account and contribute directly from the app. This might not be relevant for a mainstream map app but I don't think we're looking for mainstream given the demographics of mobile linux.

I chose "work well with low spec devices" highly but I actually mean "good performance". Mobile osm maps are often vector based and tend to be slow on phones (even on android). But I think this can be fixed by using appropriate algirithms, gpu acceleration and a focus on performance (or by using a mixture between tiles and layers).