Firefox/Accounts/Progress Report/2017Q3

September 18, 2017

Q3 OKR Progress

Objective	Key Result	Confidence	Features	Notes
Jul 10	Jul 24	Aug 8	Aug 21	Sep 5	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%	70%	75%	90%	100%		Priorities for support of Quantum/Photon in 57: Crouton Flow Issues for 57 release.	Done! Crouton Flow Burndown Chart
	1.2 Close 50% of our Q3 quality backlog.		50%	75%	75%	90%	100%		Quality Priorities for Q3: Quality related P1s that we’ve identified to fix in Q3.	Done! Quality P1s Burndown
	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%	50%	40%	0%	0%		Supports the onboarding team, marketing retention team and Mozilla.org team to improve user retention (through converting first run users to multi-device users). Dashboards related to user retention Issue 5332: ABC test for CAD phase 3 (deep link)	Still not seeing any difference in outcomes between the different phases in our ABC test. Landed our iOS deeplink patch on Sept 7th so signinCodes consumption should have increased since that date. Form views on iOS should also have increased since that date thanks to deeplinks. Leif will compare form views per phase. The bottom charts of our dashboard are not measuring phase 2 and 3 the same way. They show very different results because phase 3 uses the flow_id. There may be a bug with the flow_id so Leif will copy the phase 2 chart for phase 3. Will see what difference that makes.
	1.4 Fix newsletter subscription when email is confirmed on a 2nd device.	95%	95%	95%	95%	90%	90%		Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.	Not sure if the fix is working. Ryan is going to put together a test plan to confirm it.
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%	55%	55%	50%	50%		FxA Sync prioritization backlog for iOS Proposed mock up	Bug to set up a feature flag for it. Should be able to get into 9.1 and do an A/B test with the beta users. Probably won’t be able to declare this a success within this quarter.
	2.2 Complete 80% of Q3 mobile bugs.	N/A	60%	60%	60%	65%	90%		Identification and fixing of the most impactful bugs on iOS Mobile Bugs for Q3 Currently working on: Issue 5279: Update Confirm view to handle when verification is using Push Issue 335: Display FxA avatar in settings [bz1382756] Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]	70% of the 80% are done. Probably won’t reach 80%, but confident that we’ll be close. Mobile Quality Burndown Chart
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%	50%	25%	0%	0%		Allow users to test out device pairing. This does not necessarily mean that QR codes are used. Feature doc and issues coming soon.	Not going to happen this quarter. This KR is about device pairing. What we tried with QR code hasn't worked out.
	3.2 Ship secondary email.	80%	80%	90%	90%	90%	90%		We are allowing users to add a secondary email. Allows users to change primary email. Issues for changing primary email: Issue 278: Add ability for a FxA user to change their primary email Issue 341: Detect when account email has changed, and update local state to match Issue 1999: (node:48) DeprecationWarning: DeprecationWarning for mem.emailRecord: Use mem.accountRecord Issues 341: Detect when account email has changed, and update local state to match	Android side is close to being done. Pretty confident this one is going to happen. We should be able to wrap up the server 2 side bugs (500 errors). Getting ready to test again.
	3.3 Land support for relier encryption keys.	70%	70%	75%	75%	75%	80%		Relier encryption keys	Crypto consultant started today. Issue 245: Prototype key support api for Firefox Notes
	3.4 Integrate 100% of high priority Amplitude events.	75%	75%	75%	75%	75%	90%		Implementation of Amplitude	Feel good about having data in place in time for the training. Logging 2.0 is sending the data over. Should be able to start doing the backfill using the same process.