1014406 - (migratesync) [User Story] Migrate legacy-sync users to FxA sync

Status: RESOLVED FIXED

(Firefox :: Sync, defect)

Description

[Mark Hammond [:markh] [:mhammond]]

This bug is a meta-bug for the migration of all legacy sync users to FxA-based sync.

Comment 1

[Mark Hammond [:markh] [:mhammond]]

TIL that not all components have "user stories" enabled.  My first cut at a user-story, pending UX, is:

* Fx will begin to display a gray "warning" notification that Sync needs to be upgraded, and offers a link to start the process.  If the user closes the prompt, it will continue to be re-displayed periodically.

* At some point, the notification will change to an "error" notification indicating that Sync is no longer functioning, and offers a link to start the migration process.

* User accepts the offer to migrate.

* Normal FxA "sign-up" process is initiated, with the existing sync account-name the default email address.

* Behind the scenes, Sync will perform a complete sync, update the old sync's record for the device with the FxA account name, then perform a full FxA sync.

* A "success" page will be shown.
** If sync account has other associated devices that are not yet migrated , this page will include a note that the other devices should also be upgraded.
** If no other associated devices, this page will include a note that the process is now complete.

* User starts Firefox on alternate device.

* Alternate device will notice that other devices for the account have migrated, and offer to migrate this device.

* User accepts, Fxa "sign-in" flow is shown with the FxA account name pre-filled.

* As above, a full sync is done with the old account, then the device record updated, then a full sync with the FxA account.

* As above, the "success" page is shown with the same variation (ie, indicate there are still more devices, or we are complete).

* Profit?

Comment 2

[Mark Hammond [:markh] [:mhammond]]

Gavin and I discussed this a little, and we can't see a great reason to force a complete sync before migrating to FxA - even if all clients aren't consistent, they should become consistent after they all migrate.  There might be obscure edge cases (eg, another device did a sync before dieing, and so new data on that subsequent device might be lost) but it doesn't seem worth worrying about.

This has the added bonus of not requiring special handling and UX for clients that can't perform a complete sync (eg, due to places database corruption) - they will still be left with the corruption and not able to complete an FxA-sync, but at least they are on FxA - ie, it means we need not bother with bug 1014415.

What this *does* mean is that we will still need to perform an explicit sync of the "clients" engine, so we can write metadata that reflects the client was upgraded - I'll open a new bug for that.

If there are no objections to this, I'll close bug 1014415.

Comment 3

[Mark Hammond [:markh] [:mhammond]]

No longer depends on bug 895518 as that also covers android - but blocking on bugs under that tree that are relevant to this desktop meta bug.

Comment 4

[Ryan Feeley [:rfeeley]]

USER FLOW DIAGRAM
https://www.lucidchart.com/publicSegments/view/53960efc-4b5c-484a-bcd5-13930a00de31/image.pdf

SCREENS
https://www.dropbox.com/s/l0us0kr2zr4htx9/Sync%20Migration.pdf

USER STORIES

So that I can continue syncing, as legacy Sync user on a pre-31 version of Firefox, I want to be notified about my need to update Firefox.

So that I can prepare for the deprecation of legacy Sync, as a legacy Sync user, I want to be notified about deprecation but also be given the option to create a Firefox Account.

So that I can do something about sync being broken, as a legacy Sync user after Sync has been ended, I want to be notified about deprecation but also be given the option to create a Firefox Account.

So that I can browse the web uninterrupted, as a legacy Sync user, I want to be able to dismiss upgrade notifications temporarily.

So that I can browse the web uninterrupted, as a legacy Sync user, I want to be able to dismiss upgrade notifications permanently.

So that I remember to connect my other devices, as new Firefox Account holder on my other devices, I want to be notified about my need to sign in to my new account.

So that I know that I have activated the new Sync successfully, as user who is adding his/her first or subsequent devices, I want to be notified about sync working.

So that I can avoid retyping, as a legacy Sync user who is upgrading an old account that has an email address username, I want my username to be pre-populated on the Registration form.

So that I retain my original Sync settings, as a legacy Sync user who is upgrading, I want my sync datatype selections to be remembered.

Comment 5

[Mark Hammond [:markh] [:mhammond]]

I think we'll keep this one opened for now - the UX bug 1014412 should be closed once we've nailed all UX components - but I'm not closing that one for now as I just added 2 new blockers :)

Comment 6

[Ryan Feeley [:rfeeley]]

Hi Mark, here is a complete vision for the migration experience (download this PDF which links to other PDFs) that includes notification bars, preferences, the Australis menu and more.
http://is.gd/sync_migration_ux_pdf
Covers the gamut.

Comment 8

[Ryan Kelly [:rfkelly]]

Hi Mark, is there any useful work remaining under this bug tree, or can we close it out?  I get the strong feelig that anything that ain't done as of now, ain't gonna get done at all :-)

Comment 9

[Mark Hammond [:markh] [:mhammond]]

(In reply to Ryan Kelly [:rfkelly] from comment #8)
> Hi Mark, is there any useful work remaining under this bug tree, or can we
> close it out?  I get the strong feelig that anything that ain't done as of
> now, ain't gonna get done at all :-)

Bug 908463 remains open, but I suspect will not for long, so yeah, let's call this done!