Include seedvault as a generic backup application/backend
Seedvault is a generic backup application for Android.
It completely replaces the Google cloud backup.
This feature concerns
Now there is a problem: As it uses internal APIs, it does not only need to be installed as a system-app, but the app also needs to be signed by the platforms private key. See https://github.com/stevesoltys/seedvault/issues/8 for that statement.
Thus, installing afterwards on Android is not possible.
Now, I know, that you maybe also made adjustments to the same components for use with your e.could services.
However, I'd still like to have this application here, because people may want to use a different self-hosted Nextcloud instead of your e one or another backup location.
Who will use the new feature?
Anyone who wants a different backup application than /e/ cloud. And who does not want Google neither, obviously.
Basically, likely advanced users, who have their own Nextcloud.
What is the target of the new feature for this user?
Backup to their own Nextcloud an external drive or similar things. Also: It's e2e encrypted.
Why this user would like to use this feature?
Privacy, security (e2e encrypted), a general nice interface…
User can use their own Nextcloud with any size limit they want.
Also other backup providers, which are added in the future – e.g. things like seafile, will then automatically be supported once you pull the upsteam changes in here.
If users do not use your cloud services for backup, this takes off stress from your servers.
I don't know your backup integration, but IMHO you'd best to just integrate your one in the seedvault/a fork of seedvault, so you can get in upstream changes from seedvault too, anyway.
I've advocated for this before in LineageOS, but I guess /e/ has a focus on privacy and this is certainly a privacy-enhancing project, which I think makes kit more realistic to be included here.
Have a look on how it works: