MozillaWiki

Firefox/Accounts/Progress Report/2017Q3

< Firefox‎ | Accounts/Progress Report
Revision as of 03:07, 29 July 2017 by Juliemccracken (talk | contribs) (Entered the July 24th OKR confidence assessments)

July 24, 2017

Q3 OKR Progress

Objective Key Result Confidence Features Notes
Jul 10 Jul 24 Aug 7 Aug 21 Sep 4 Sep 18 Score
1. To have improved the quality for the Firefox Account experience on desktop. 1.1 Close ALL (100%) issues in the Quantum/Photon milestone. (Crouton) 60% 65%

Active in this sprint:

  • Fixed 11 issues already, with 15 to go.
  • Working on the remove single button state for Train-93.
  • Need strategy to attack the non-bmp characters in device names with non bmp characters (issue 1285).
  • Crouton Flow Burndown Chart
1.2 Close X% of our Q3 quality backlog. 50%

Active in this sprint:

  • Initial confidence assessment wasn't based on much data
  • Quality P1s Burndown shows we’re on the ideal line
1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow. 50% 50%

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).

  • We've seen an increase in views but no noticeable increase in what happens after.
  • Need to start shipping some of the quality improvements before we change the confidence level.
1.4 Fix newsletter subscription when email is confirmed on a 2nd device. 95% 95%

Fix the problem of how we currently lose newsletter subscribers if users confirm their emails on a different device.

  • Merged and should ship - we have everything but the measuring.
  • Will help marketing’s metrics.
2. To have improved the quality of the Firefox Account experience on mobile.


2.1 Measure and A/B test best push opt-in screen on iOS. 50% 40%
  • Rfeely shared mock ups on how it should look. Ryan prefers it to be native. Not sure of impact of this.
  • 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.
  • Feature doc is in draft.
2.2 Complete 80% of Q3 mobile bugs. N/A 60%

Identification and fixing of the most impactful bugs on iOS

  • Came up with a list of 13 bugs that were reviewed with Stefan
  • 10 of the 13 we have high confidence in completing
3. To have completed all features that are still in flight from Q1 and Q2. 3.1 Have a device pairing flow ready to A/B test. 75% 75%

Allow users to test out device pairing. This does not necessarily mean that QR codes are used.

  • Feature doc and Issues coming soon.
  • Phil and Shane to get together to chat about a feature doc for this
  • Waiting for August 8th, when Android will support deeplinking in 55.
  • Test plan updated.
  • 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.
3.2 Ship secondary email. 80% 80%

We are allowing users to add a secondary email. Allows users to change primary email.

  • Only thing remaining is how clients would handle the change on their GUI/interfaces
  • Can disable or enable on the content server.
3.3 Land support for relier encryption keys. 70% 70%

Relier encryption keys

  • Did some work on this but not enough to change confidence further.
  • Biggest risk is not getting the crypto review done soon enough (reliance on other teams).
3.4 Integrate 100% of high priority Amplitude events. 75% 75%

Implementation of Amplitude

  • Went through Amplitude onboarding.
  • Have gotten the ball rolling with coordination.
Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Accounts/Progress_Report/2017Q3&oldid=1176845"