Not exactly 
When I started this project I hoped to not even need to write a message app UI (i.e. use signal). But in terms of the amount of work, the UI for maps and the UI for messaging were both a fairly small amount of work (though as @lgx keeps improving it becomes less small )
Once 1.0 is “out the door” (or earlier if people want - but I’m not going to engage much in such ideation right now) we can have a group chat to go through the ideas and make rough buckets for:
- 1.1 features (including a few features I deferred from 1.0) - where 1.1 is expected to complete in about two months?
- 1.5 features - which is probably sixish months from now.
There is already a very easy meshtastic API on android (and python) so if other apps want to use the mesh to do something fancier or custom they can do that also. The Android GUI app just uses the same “MeshService” android service as any other app would.
For 1.1/1.5 ideas see here: