> > We certainly have the infrastructure to do this: we do something like this > on every device right now in order to recover the Android Account across SD > card manipulations. We would want special support to do this across > devices, and I'm not sure we want to. >
To go a step beyond Nick's point: it's not entirely clear what the user expects here, which introduces the possibility of pain. If this is a *restored backup* to the *same device*, maybe they should stay signed in and keep their client name, client ID, and other metadata. If they're restoring the backup to a new device, and the old one is gone, some things would need to be discarded (e.g., the client name probably refers to the wrong hardware). If they're *cloning*, then we definitely have a lot of stuff to throw away. This all gets complicated and unpleasant, so I'd be inclined to just carry forward their email address/FxA server combo, and make them sign in again. We handle that pretty well. 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. >> > Careful migrating SharedPreferences, and even some data stores. These things interact with Sync, and will do so to an increasing extent as we shift to a model more like the one we use on iOS.
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
