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

Jump to navigation Jump to search
Corrected August 21st update
(Deleted old bullet)
(Corrected August 21st update)
Line 1: Line 1:
__NOTOC__
__NOTOC__
<big><big>'''August 8, 2017'''</big></big>
<big><big>'''August 21, 2017'''</big></big>


== Q3 OKR Progress ==
== Q3 OKR Progress ==
Line 17: Line 17:
|style="text-align: center; background-color: #f9d9a8"|Aug 8
|style="text-align: center; background-color: #f9d9a8"|Aug 8
|style="text-align: center; background-color: #f9d9a8"|Aug 21  
|style="text-align: center; background-color: #f9d9a8"|Aug 21  
|style="text-align: center; background-color: #f9d9a8"|Sep 4
|style="text-align: center; background-color: #f9d9a8"|Sep 5
|style="text-align: center; background-color: #f9d9a8"|Sep 18
|style="text-align: center; background-color: #f9d9a8"|Sep 18
|style="text-align: center; background-color: #f9d9a8"|Score
|style="text-align: center; background-color: #f9d9a8"|Score
Line 37: Line 37:
*[https://github.com/mozilla/fxa-auth-db-mysql/issues/229 Issue 229: Update device name column to utf8mb4]
*[https://github.com/mozilla/fxa-auth-db-mysql/issues/229 Issue 229: Update device name column to utf8mb4]
|
|
*Fixed additional bugs in the past sprint. 25% remaining to fix, down from 37%.
*25% remaining to fix. Fixed some bugs this cycle.  
*Animation on svg’s needs to be started ([https://github.com/mozilla/fxa-content-server/issues/5168 Issue 5168: Discuss how we should animate new illustrations]).
*Animation on svg’s needs to be started. Once we’re done with the non-BMP char device names (unicode), that will free up some time (#5 on the list).
*Once we’re done with the [https://github.com/mozilla/fxa-auth-server/issues/1285 Issue 1285: Device names with non-BMP characters are rejected], which is priority #5 on the list, that will free up some time.
*Rest seem pretty manageable but just need to get them to the top of the list.
*Rest seem pretty manageable but just need to get them to the top of the list.
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Burndown Chart]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Burndown Chart]
|-
|-
Line 60: Line 58:
*[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]
*[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.
*Following desired burn-down pace.
*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.
*Anything that needs browser work? Yes #5197 requires a browser patch. Never send users to about: preferences after Sign-in
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] shows we’re on the ideal line
*Prioritize 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. #5196 #5009 #5197
 
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown]
|-
|-
|align="left"| 1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow.
|align="left"| 1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow.
Line 79: Line 79:
*[https://github.com/mozilla/fxa-content-server/issues/5194 Issue 5194: Sign-up/in flow: Ask for email first]
*[https://github.com/mozilla/fxa-content-server/issues/5194 Issue 5194: Sign-up/in flow: Ask for email first]
|
|
*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?
*Now that we’re using strict multi-device, numbers are going down, leading us to have less confidence.
A/B/C testing is set up as follows:
*Uptick in engage but no change in ?
**Mobile Push (Phase 1) for ⅓ of the users
*Graph not moving in the right direction
**Mobile Push (Phase 2) for ⅓ of the users
*Try to show CAD screen more often
**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.
|align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device.
Line 98: Line 95:
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
|
|
*Didn’t seem to be any big change in marketing's metrics after fixing the problem. Marketing is expected to look at the metrics again.
*Didn’t seem to be any big change in their metrics. Marketing is expected to look at them again.
*Number didn’t drop to 0, so we didn’t break it. It was trending down even before our work landed. So not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.  
*Number didn’t drop to 0 so we didn’t break it.
*Trending down even before our work landed. So not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.  
|-
|-
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
Line 134: Line 132:
*[https://github.com/mozilla/fxa-bugzilla-mirror/issues/332 Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]]  
*[https://github.com/mozilla/fxa-bugzilla-mirror/issues/332 Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]]  
|
|
*No PRs have been merged yet.
*Did the easy ones first. Medium level ones are left to do. Should have 9/13 done by next week.
*FxA iOS verification links open at almost the same rate as iOS for sign-in, ~45%. This is a significant increase over 8% previously. [https://github.com/mozilla/fxa-bugzilla-mirror/issues/337 Issue 337: Open FxA verification links in Fx for iOS [bz1382776]]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
|-
|-

Navigation menu