No, it should be local-first. Private and offline by default. There could certainly be sync integrations using AT, Dropbox, iCloud, etc. Those could even be separate apps, using the same API to access the data. But that sort of thing should be secondary and optional.
Comments
No, it should be local-first. Private and offline by default. There could certainly be sync integrations using AT, Dropbox, iCloud, etc. Those could even be separate apps, using the same API to access the data. But that sort of thing should be secondary and optional.
OsmAnd already can store an unlimited amount of POIs locally. With text, icon, color, coordinates of corse.
Do you have any thoughts on data structure for local storage?
We already do local bookmark backup, and use KML natively I think. It just doesn't sync, resolving sync conflicts is hard.
Not really. I imagine a sqlite db, but I haven't thought about any particular schema.