ActivityRecommender stores data and provides the ability to do backups and transfers of data by exporting all of the data as a single file.
This means that if the user makes a backup (to their device's external storage directory) on each of several different days, there will be multiple backup files, and a bunch of duplication among them.
It could be interesting to find a way to reduce this duplication.
Currently, the only way to reduce this duplication is for the user to manually delete any unwanted files. They're all in one directory, though, to make it easy to delete all of them at once if desired. Is that sufficient?
It would be nice if the backup strategy doesn't connect to the internet so that users can be confident that ActivityRecommender isn't sharing their data with unexpected entities
ActivityRecommender stores data and provides the ability to do backups and transfers of data by exporting all of the data as a single file.
This means that if the user makes a backup (to their device's external storage directory) on each of several different days, there will be multiple backup files, and a bunch of duplication among them.
It could be interesting to find a way to reduce this duplication.
Currently, the only way to reduce this duplication is for the user to manually delete any unwanted files. They're all in one directory, though, to make it easy to delete all of them at once if desired. Is that sufficient?
It would be nice if the backup strategy doesn't connect to the internet so that users can be confident that ActivityRecommender isn't sharing their data with unexpected entities