osmscout-server VS fdroiddata

Pure Maps with OSM Scout Server for offline mapping and geolocation

- build a minimal web page showing a Leaflet or a MapLibre widget, connected to a backend built using a compiled language like C++ or D, itself connecting to OSM Scout Server to provide the tiles. Or to OSM Scout Server directly if it is possible.

The last option is probably the most lightweight solution, provided you probably have a browser already running on your phone. I'm not saying this out of my ass by the way, I'm building an SMS app using Svelte for the user interface and D for the backend connecting to the modem and managing the SQLite database. It's way faster than chatty.

[1] https://openrepos.net/content/rinigus/pure-maps

[2] https://rinigus.github.io/osmscout-server/

There are on device or even in browser renderers that only need remote or locally stored vector data to render the map. This moves the burde of rendering to user devices that should be more than capable for this today (especially if you use a GPU renderer) and makes you server into just a dumb data pipe that should be able to scale much better & more cheaply.

One such renderer available via Qt/QML:

https://doc.qt.io/qt-5/location-plugin-mapboxgl.html

Alternatively you can have a local daemon running that does the tile rendering on your device from offline data packs. This way even "legacy" apps requiring simple bitmap tiles will work without (major) changes. One such project providing this (among other APIs) is OSM Scout Server:

https://github.com/rinigus/osmscout-server

Fork this repository.

For reference my app: project: https://github.com/balzack/databag merge request: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12183

You should add a new entry in "Builds". Have a look at how Newpipe does it for each new version here for example.

To me it's not very clear whether those terms practically apply only to their app, since clearly they can't grab logs from Aurora if Aurora doesn't dump those logs for example... but if this is something the F-Droid team should look into, open an issue on https://gitlab.com/fdroid/fdroiddata/-/issues or inquire in one of their official channels on OFTC (#fdroid) or Matrix (#fdroid:f-droid.org).

OsmAnd~ from F-Droid not having Android Auto is a known bug: see the discussions at https://gitlab.com/fdroid/fdroiddata/-/issues/2567 , https://github.com/osmandapp/OsmAnd/issues/13514, https://github.com/osmandapp/OsmAnd/issues/3391 and https://github.com/osmandapp/OsmAnd/issues/15400

You can also get F-Droid Build Status which I believe will let you see apps that are being attempted to be built even if their build isn't succeeding yet, again for the "catching things early experience". Or, just keep an eye on the issues, merge requests and commits at fdroiddata which is where people actually add new metadata for new apps to be built by F-Droid, and it often takes a while between an app being first mentioned, and it being able to be included, for many possible reasons.