#android #FOSS folks, is there a gap in the automated #DataExport / #backup space?
I use #OpenTracks to track fitness activities (it's not quite the Google Fit replacement I was hoping it would be: See https://github.com/OpenTracksApp/OpenTracks/issues/1587) and #OsmAndMaps, and I use Nextcloud. However, backing up my cycling/walking/running tracks from OpenTracks and my bookmarks from OsmAnd to Nextcloud requires manual action.
If this is indeed a gap, I was thinking of putting up an open source recurring automated data export protocol for public comment.
1. Any data producing app (like OpenTracks) can include a small library that implements the protocol, allowing users to define the automated recurring data export frequency, how many old backups to keep etc.
2. Any data backup app (like Nextcloud) can include a different library that broadcasts an intent at a regular frequency that all protocol-compliant data producing apps can handle. When the broadcast is received, data producers can generate/hand over the file(s) to be backed up by the data backup app.
I'm tempted to build a #WebDAV-compliant open source app as well (as an example of a protocol-compliant data backup app) but that might be a grand undertaking.
Thoughts?
#DataSovereignty #decentralization #androiddev #opensource #OSM