Multi-device sync/recover capability

[Fmstrat]

Describe the feature
If open to it, considering authoring a PR for full-sync and recover. This is similar to previous sync requests like backing up to cloud providers, but would handle the sync the same way applications like Steam or Google Play do.

UI additions:

• Toggle for sync
• Sync server URL selection
• Device name (defaults based on similar name pattern to Firefox)
• Sync credentials
• Additional dropdown on restore screen for "Install to match /none
• In each app details, a list of "Installed on" devices

Backend additions:

• Current backup format in JSON is used, but
  • Each installed app gets an Installed On array of devices
• When opening Obtainium and/or adding a new app, a sync occurs
• Adding apps is not allowed if sync fails
• When installing/uninstalling/removing, a date time flag to indicate action is added in an Actions array
• Removing an app keeps the app in the configuration, but hides it from the UI

Sync method:

• For each app, whichever Action has the latest date (device or server) is used
  • If server has newer action than device, and server says installed for the current device but device says it is not, an Action of ResolveUninstalled is added to the array and saved in both locations
    • This is ignored if "restore" is in progress
    • Potential v2 revision to this to allow for "install on another device"

Still debating on the sync server infrastructure. I could pretty easily make a docker-based service with a postgres DB, but users may prefer a selection of cloud providers like Drive and Nextcloud. The advantage of the former is you (or anyone) could run a multi-user sync service, which could be a pathway to revenue if you so desired (I would only submit a PR under the current license, though).

Describe alternatives you've considered (if applicable)

Current export/import

Additional context

I want to be able to use Obtainium across multiple devices fully de-googled. This would be a lot easier if Obtainium supported a centralized account structure.

[Fmstrat]

I should.probably note, I have a good bit of experience in sync. I authored OwnNote for OwnCloud, a sync service for Plex, an Rclone system for Steam Deck retro game save sync, and many moons ago helped debug port issues with Firefox Sync.

[ImranR98]

I have closed similar issues in the past because it's not something I would undertake (usually issues I don't plan to work on do remain open for others to contribute, but I didn't think there would be any PRs for something this big). But if you're planning to contribute a PR, that would definitely be accepted after review. Personally I'd prefer the Docker-based self-contained option since it's less hassle (Nextcloud has always been very frustrating/buggy for me) but that's up to you of course. And yes, the license is not going to change.

I don't know if you've looked at any code yet (it's a mess). Obtainium currently stores the app config and install state in the same file, so I guess a prerequisite for any sync work would be to first separate them (and associated save/load functions).

[Fmstrat]

@ImranR98 Sounds good, I'll take a look. Perhaps I'll start by taking the config and building the server-side aspects so I can get the backend to a point of acceptable use before going too deep into the app code, though at a glance it doesn't seem more complex than other projects.

This may take me a while since I don't have that much spare time, but if you don't mind this issue hanging around for lurkers, I'll start a draft PR at some point and ping this issue.

[Fmstrat]

We could probably include E2E encryption, and running a server on a $5 a month Linode would be more than enough to support the entire community, too.

@Fmstrat Why not just use a file synchronization application with a elevated previleges (may require devices that are rooted if the file synchronization application doesn't support elevated privileges using something that uses ADB to access /Android/data) and sync the contents of /Android/data/dev.imranr.obtainium/files? I think something like an inbuilt synchronization feature should not be added to Obtainium. It will likely also significantly increase the application's size.

[Fmstrat]

Why not just use a file synchronization application with a elevated previleges (may require devices that are rooted if the file synchronization application doesn't support elevated privileges using something that uses ADB to access /Android/data) and sync the contents of /Android/data/dev.imranr.obtainium/files?

Because most people don't run apps with elevated privileges, and unfortunately that's not a reliable structure to maintain since there are third-party requirements. But also, that won't work. As soon as you upgrade on one device and that syncs to a device that isn't upgraded (Obtainium or any app in the list), you run into a potential conflict. Also, users may not want the same apps installed on different devices, but rather a selection of their overall app library, just like on Google Play. Tablets and phones often have different use cases.

I think something like an inbuilt synchronization feature should not be added to Obtainium.

Why not?

It will likely also significantly increase the application's size.

What makes you think this? Obtainium already has the libraries for HTTP calls.

Why not just use a file synchronization application with a elevated previleges (may require devices that are rooted if the file synchronization application doesn't support elevated privileges using something that uses ADB to access /Android/data) and sync the contents of /Android/data/dev.imranr.obtainium/files?

Because most people don't run apps with elevated privileges, and unfortunately that's not a reliable structure to maintain since there are third-party requirements. But also, that won't work. As soon as you upgrade on one device and that syncs to a device that isn't upgraded (Obtainium or any app in the list), you run into a potential conflict. Also, users may not want the same apps installed on different devices, but rather a selection of their overall app library, just like on Google Play. Tablets and phones often have different use cases.

I think something like an inbuilt synchronization feature should not be added to Obtainium.

Why not?

It will likely also significantly increase the application's size.

What makes you think this? Obtainium already has the libraries for HTTP calls.

Because the code is probably complicated. I don't think a feature like this should be in Obtainium. It's not that hard to maintain the same configuration on multiple devices.

[Efreak]

Can I suggest including an option for simple SAF backend? Assuming this is possible in some way.