MozillaWiki

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

Page Discussion

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

Revision as of 01:21, 10 August 2017

1,564 bytes added ,  10 August 2017
Finished updates
(Updated 1.2)
(Finished updates)
Line 68: Line 68:
|align="center"|
|align="center"|
|
|
The onboarding team, marketing retention team and Mozilla.org team would like our help to improve user retention (through converting first run users to multi-device users).
*Supports the onboarding team, marketing retention team and Mozilla.org team to improve user retention (through converting first run users to multi-device users).
*Ask for email first: Instead of a user needing to know to "Sign In" or "Sign Up", they visit the "Connect to Firefox Accounts" (or similar) page, where they simply enter their email. We determine if an account exists and forward the user to the appropriate sign in or sign up screen.
*[https://sql.telemetry.mozilla.org/dashboard/fxa-q3-okr-1-3 Dashboards related to user retention]
*[https://sql.telemetry.mozilla.org/dashboard/fxa-q3-okr-1-3 Dashboards related to user retention]
*[https://github.com/mozilla/fxa-content-server/pull/5332 Issue 5332: ABC test for CAD phase 3 (deep link)]
*[https://github.com/mozilla/fxa-content-server/issues/5194 Issue 5194: Sign-up/in flow: Ask for email first]
|
|
*We've seen an increase in views but no noticeable increase in what happens after.
*Still waiting for some things to ship.
*Need to start shipping some of the quality improvements before we change the confidence level.
*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.
 
*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
|-
|-
|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 83: Line 92:
|align="center"|
|align="center"|
|
|
Fix the problem of how we currently lose newsletter subscribers if users confirm their emails on a different device.
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
|
|
*Merged and should ship - we have everything but the measuring.
*Merged and should ship - we have everything but the measuring.
Line 101: Line 110:
|align="left"|
|align="left"|
*[https://docs.google.com/spreadsheets/d/1tPE4KSNd_RU-ahSAK7a5hMcP5EAKGMlHJHegna87xLg/edit#gid=0 FxA Sync prioritization backlog for iOS]
*[https://docs.google.com/spreadsheets/d/1tPE4KSNd_RU-ahSAK7a5hMcP5EAKGMlHJHegna87xLg/edit#gid=0 FxA Sync prioritization backlog for iOS]
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
|
|
*Rfeely shared mock ups on how it should look. Ryan prefers it to be native. Not sure of impact of this.
*Met on August 8 about conducting an A/B test with LeanPlum.  
**[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
*Documentation makes it look reasonable.
*We don’t think iOS app. itself has something built in to perform the A-B test. Might be best to make it web based and use our own tools.
*There’s an ability to dynamically create strings within their interface. They’ll handle all the strings so we don’t have to deal with that.
*Feature doc is in draft.  
|-
|-
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
Line 119: Line 128:
*[https://waffle.io/mozilla/fxa?milestone=FxA-132:%20Q3%20Mobile Mobile Bugs for Q3]
*[https://waffle.io/mozilla/fxa?milestone=FxA-132:%20Q3%20Mobile Mobile Bugs for Q3]
|
|
*Came up with a list of 13 bugs that were reviewed with Stefan
*Pull requests but they haven’t been merged yet.
*10 of the 13 we have high confidence in completing
*Top priority for train-94 is getting in all the iOS prefs stuff.
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
|-
|-
|rowspan=4| 3. To have completed all features that are still in flight from Q1 and Q2.
|rowspan=4| 3. To have completed all features that are still in flight from Q1 and Q2.
Line 135: Line 145:
*Feature doc and Issues coming soon.
*Feature doc and Issues coming soon.
|
|
*Phil and Shane to get together to chat about a feature doc for this
*Tried QR scanner on phone and it failed. Scanning doesn’t work on pixel phone in fx because it doesn’t auto-focus.  
*Waiting for August 8th, when Android will support deeplinking in 55.
*Will try Chrome Android phone to see if it works there. Looking at the specs. Looks like there’s an auto vs. manual focus option.
*Test plan updated.
*Might need to make use of built-in scanner as part of Firefox mobile or something else. Need to figure out another way around this.
*Plan is to enable it in train-93 because 55 will be out at that point.
*We need to think about anything we need to get into 56 beta.
|-
|-
| align="left"|3.2 Ship secondary email.
| align="left"|3.2 Ship secondary email.
Line 150: Line 158:
|align="center"|
|align="center"|
|
|
We are allowing users to add a secondary email. Allows users to change primary email.
*We are allowing users to add a secondary email. Allows users to change primary email.
*Issues for changing primary email:
**[https://github.com/mozilla/fxa-bugzilla-mirror/issues/278 Issue 278: Add ability for a FxA user to change their primary email]
**[https://github.com/mozilla/fxa-bugzilla-mirror/issues/341 Issue 341: Detect when account email has changed, and update local state to match]
**[https://github.com/mozilla/fxa-auth-server/issues/1999 Issue 1999: (node:48) DeprecationWarning: DeprecationWarning for mem.emailRecord: Use mem.accountRecord]
**[https://github.com/mozilla/fxa-bugzilla-mirror/issues/341 Issues 341: Detect when account email has changed, and update local state to match]
|
|
*Only thing remaining is how clients would handle the change on their GUI/interfaces
*Change email passed the SV testing.
*Can disable or enable on the content server.
*Should be enabled for all users in train-93.
*Client side patches (ios profile). Still working on iOS part
|-
|-
| align="left"|3.3 Land support for relier encryption keys.  
| align="left"|3.3 Land support for relier encryption keys.  
Line 166: Line 180:
Relier encryption keys  
Relier encryption keys  
|
|
*Did some work on this but not enough to change confidence further.
*Now we have prototype for test pilot mobile apps.  
*Biggest risk is not getting the crypto review done soon enough (reliance on other teams).  
*[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes]
|-
|-
| align="left"|3.4 Integrate 100% of high priority Amplitude events.  
| align="left"|3.4 Integrate 100% of high priority Amplitude events.  
Line 180: Line 194:
Implementation of Amplitude
Implementation of Amplitude
|
|
*Went through Amplitude onboarding.
*Amplitude is comfortable with our taxonomy
*Have gotten the ball rolling with coordination.
*In a position to start integration
*Break down of the work needs to be placed in Github
 
|-
|-
|}
|}
Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1177824"