To recount today's Frontend meeting, we briefly spoke about conflict between Firefox Sync & auto backup. We came up with the possibility of syncing the Firefox Account Android-account so that when users switch to a different device, Sync will be automatically set up and the Firefox Sync services can restore the user's synced data (e.g. this could help differentiate Firefox and maintain retention on new devices). It's unclear if Firefox Sync will allow us to do that under the hood, but it's open to be investigated.
We didn't discuss other data to potentially store – files, databases, and shared preferences, as Sebastian mentions above. I personally think it'd be great to save preferences as well, though I'm unsure how this could affect the Gecko-related preferences. However, I think with a bit of work, we could get preference sync working properly for preferences in the Android UI (e.g. mirror the prefs in shared preferences so Android can restore them). I think this is lower priority than the account work. - Mike On Mon, Oct 12, 2015 at 1:57 AM, Sebastian Kaspari <[email protected]> wrote: > Hey everyone! > > I have been looking into bug 1190375 [1] - "Create whitelist (or > blacklist) for Android Auto Backup" and need some input from you! > > Background: > * Android 6.0 automatically creates backups of application data and > accounts (for apps with targetSdkVersion >= 23) > * When the app is (re-) installed Google will download and restore > application data from the backup > * The backup is independent from the device. Switching to a new device > will restore the backup from a previous device. > * Each app can store up to 25 MB > > https://developer.android.com/training/backup/autosyncapi.html > > We want to create a whitelist of things that Google can safely backup and > restore across devices. But what should we add? My first intention was to > add our preferences to that whitelist. But some of them are actually > Gecko-related things and not just simple shared preferences. > > So what should we add? Files, databases and shared preferences are good > candidates. > > Sebastian > > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1190375 > > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev > >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
