Firefox/Accounts/Progress Report/2017Q3: Difference between revisions

Firefox/Accounts/Progress Report/2017Q3 (view source)

Revision as of 21:39, 23 August 2017

1,078 bytes added , 23 August 2017

Added 1.2 and 1.3 updates

Juliemccracken

670

edits

@@ Line 48: / Line 48: @@
 |align="center"|50%
 |align="center"|75%
-|align="center"|
+|align="center"|75%
 |align="center"|
 |align="center"|
 |align="left"|
 |
+Quality Priorities for Q3:
 *[https://waffle.io/mozilla/fxa?milestone=FxA-131:%20Q3%20 Quality related P1s that we’ve identified to fix in Q3.]
 Active in this sprint:
-*[https://github.com/mozilla/fxa-content-server/issues/5203 Issue 5203: Device Manager: Make device icons accurate]
+*[https://github.com/mozilla/fxa-content-server/issues/5196 Issue 5196: Sign-up/in flow: Don't ask to connect a mobile device when you started flow on mobile]
-*[https://github.com/mozilla/fxa-content-server/issues/4863 Issue 4863: Add descriptions to Choose What to Sync]
+*[https://github.com/mozilla/fxa-content-server/issues/5197 Issue 5197: Sign-in flow: Never send users to about:preferences after Sign-in] requires a browser patch.
-*[https://github.com/mozilla/fxa-content-server/issues/4857 Issue 4857: Firefox Android is having trouble with signin confirmation]
+*[https://github.com/mozilla/fxa-content-server/issues/5009 Issue 5009: Only show "email verified" on /connect_another_device if the user actually verfied their email.] confirmation]
 |
 *Continue to burn down issues along the projected ideal line.
+*Prioritizing sign in/sign up flow for train-95. Know what we shouldn’t do but not necessarily what we should be doing. Trying to narrow down a solution that will work for everyone.
 *[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] shows we’re on the ideal line
 |-
@@ Line 66: / Line 68: @@
 |align="center"|50%
 |align="center"|50%
-|align="center"|
+|align="center"|40%
 |align="center"|
 |align="center"|
@@ Line 77: / Line 79: @@
 *[https://github.com/mozilla/fxa-content-server/issues/5194 Issue 5194: Sign-up/in flow: Ask for email first]
 |
-*Still waiting for some things to ship.
+*FxA team's A/B/C testing continues. Now that we’re measuring "strict multi-device", numbers are going down. Confidence level for this key result has dropped because of questions around why this is happening. Maybe try to show CAD screen more often?
-*Need to look into the metrics to question whether or not users with device ID who show a different device ID within the same 7 day period are still using the first device.
+A/B/C testing is set up as follows:
-*Working on "email first" flow and sign-in code
-*In train 93 will enable:
 **Mobile Push (Phase 1) for ⅓ of the users
 **Mobile Push (Phase 2) for ⅓ of the users
 **Mobile Push (Phase 3) for ⅓ of the users
+*Marketing is evaluating the effectiveness of copy variations for the sign in/sign up flows. Their hypothesis: If we provide users with clear and concise copy about the features and benefits they’ll find in using a Fx account they’ll be more likely sign up, increasing conversions in the page and contribute to improved overall DAU/MAU. (Secondarily, users with Fx Accounts that are not logged in will find the new copy compelling enough to login.)
+*Much of the Email First work will ship week of Aug 28 as part of Train-94. Before this feature is offered to users, rigorous internal testing must be conducted because of the scope of the change, and the marketing copy experiment will need to have completed.
 |-
 |align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device.