1271778 - [UX] Come up with a design for how to surface the fact that data has been automatically migrated (including any errors?) and offer the user an opt-out

Status: RESOLVED INCOMPLETE

(Firefox :: Migration, defect, P3)

Description

[:Gijs (he/him)]

After automatically importing the user's data, we need to tell them this has happened, and we need to give them a way to "start with a clean slate". We need a concrete plan for how we intend to do that, including designs for both the notification that it happened and the option/functionality to "undo" that initial import. The first feels like it can be more transient, but per discussions with Michael and Justin, it feels like we want to give the user the option to "change their mind" about the data "up to a point", which suggests more permanent UI somewhere/somehow (where we then also need to make sure it doesn't become annoying / there's a way to dismiss it).

For both of these we'll need a visual design including some string love for the messaging we do to make sure users are happy and don't feel like we're playing hard and fast with their data or that they cannot get rid of data that maybe (for whatever reason) they don't want.

Comment 1

[:Gijs (he/him)]

Michael, if you want to split the UX work for the surfacing of the migration and the undo stuff, that works too, but it seemed like the designs would be likely to be intimately related so I kept them in the same bug for now. Feel free to adjust!

Comment 2

[:Gijs (he/him)]

One more thing: we should consider what to do if the migration was attempted but failed (partially). I'm guessing we'll want to gloss over that fact as we do now, but I recall from our meeting that the fact that some things might be broken without us explicitly telling you that was surprising to :verdi, so it seems like making a conscious decision on how to handle that here would be a Good Thing.

Comment 3

[:Gijs (he/him)]

Michael, this is the main thing blocking rolling this out on Nightly to get some initial data about impact of the feature to evaluate how much to invest in polishing it. What's the status of (alternative to newtab which we don't seem to be getting rid of just yet) UX/UI for this so we can try running this on beta (for en-US only so we can uplift through string freeze) ?

Comment 4

[Nicole Yee (:nicoleyee)]

whats the status of this bug? should we close it out?

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

Comment 6

[Matthew N. [:MattN]]

We tested auto-migration but later removed the code.