Migrating Fennec Users to Fenix using Firefox Account

RESOLVED INVALID

Status

enhancement
RESOLVED INVALID
2 months ago
9 days ago

People

(Reporter: adavis, Assigned: jdavidson)

Tracking

Details

Request Description
At the present time, Firefox Accounts + Sync are the primary and recommended way for users to migrate from Fennec to Fenix without losing all of their data.

We need to explore:

  1. How do we create urgency around this? (without being annoying)
  2. How do we communicate this migration efficiently?
  3. How do we communicate the risk of losing data efficiently?

We need to focus on getting users to turn on sync so that users don't lose their data.

Deadline
If we can do all the communications via Leanplum then we should have this by ~March 15th at latest which gives us time to actually start experiments in Beta so that Beta users don't lose their data on May 1st.

Implemented and out the door:

  • Beta: May 1
  • Release: June 30

Priority Level
1 = High

Priority Level Description

Company KPI:

  • Mobile Reach
  • Relationships

Application Services has a Q2 KR about:
Ensuring that most existing Fennec Sync users will be efficiently migrated to Fenix.

Supporting Information

Assignee: nobody → jdavidson
Status: NEW → ASSIGNED
Points: --- → 3

Moving back to "new" to indicate in queue. Sounds like assets are not ready for this work to begin.

Status: ASSIGNED → NEW
Flags: needinfo?(adavis)

Assets are not ready. I talked with Nicole Weber from Fenix UX, and she talked with Vesta. UX & Content will work on this at the end of May. I need to make sure Alex and Jess (from Marketing) are updated on this schedule.

(This can remain as New until end of May/June.)

Flags: needinfo?(adavis)

I suppose that this makes sense per their latest timeline for migration.

https://docs.google.com/document/d/1p8K832Dw3Jf_yrZKLekYLeEIebf4I0_qWYHHPacCbCo/edit?ts=5c8b8542#

Note for triage: Close this bug because the plan has changed. Re-open a new bug if there is something needed from UR related to new Fenix user experience.

Closing this bug because plans have changed. Please re-open a new bug if there is some work needed from UR on the topic.

Status: NEW → RESOLVED
Last Resolved: 9 days ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.