We're this on https://cartes.app, trying to push the Web further (even on mobile devices) so that you don't even need an app for most use cases.
We're this on https://cartes.app, trying to push the Web further (even on mobile devices) so that you don't even need an app for most use cases.
I'm not saying ego problems don't exist of course. But taking Osmand and making a simple general public app out of this is a huge effort (human and tech), probably more than building a side app.
We've not seen anything from their side. We don't really understand why they wouldn't want a proper Web version.
It's even worse in the non-open source world : Kagi's maps are bad. Qwant dropped their cool map project, too expensive. Ecosia has none, redirects to Google, its main competitor.
They could "just" clone cartes.app and run `bun i && bun start` and `ansible-playbook` to launch their instance of cartes.app, but we can't reach them. Or fund the project.
What's important though is that we collaborate on the tools we all use. OSM, MapLibre, Photon, Pelias, Protomaps, Motis, Brouter, etc. are all tools that we somehow share, each end-user app having their own combination of them.
We also thought like you do when outside of this world. But now, its a human problem. How to reach people and how to gain the time that it would take to collaborate ? We don't have the keys.
Maps are so often done as native apps that to my knowledge no one tried to just use the PWA capabilities to cache tiles on the Web. Of course what's hard is cache invalidation. Does the user want to update the tiles ? Never ? Daily, weekly ? Only some regions ? Or manually ?
Here's an issue about that : https://codeberg.org/cartes/web/issues/1078
It's in French, unfortunately Codeberg has no auto-translate capabilities yet.
app: https://maps.bpev.me
source: https://tangled.org/bpev.me/maps
Based on results from indexeddb pmtiles work: