Hi All, This week the Firefox Accounts team will be shipping FxA train-95 to production. Our priorities for this sprint, and the highlights that will ship in service of them, were:
Preparing metrics events to send to Amplitude: - Amplitude <https://amplitude.com/> is a new user-behaviour-centric metrics tool that we're trying out at Mozilla, and Firefox Accounts will be among the first Mozilla products to use it. - The FxA servers now emit the core set of events that will be published into the tool, letting us work on the mechanics of the "publish" step over the coming week. Stay tuned for a demo once the data starts flowing. Improving Account Management in Firefox for iOS: - We've been landing a variety of enhancements to account management for the soon-to-be-released Firefox for iOS v9.0, culminating this train in perhaps the most user-visible change: when you're logged in to Firefox for iOS, it will now show your account profile picture and display name on the settings page! - It's now possible to have Firefox for iOS use a non-standard FxA server without having to do a complete rebuild, which will be useful both for testers and for self-hosters. If you want to try it out, you'll need to v9.0 beta build and the instructions from the FxA self-hosting howto <https://mozilla-services.readthedocs.io/en/latest/howtos/run-fxa.html>. Quality Fixes from the "Crouton Flow" backlog: - Although most code in Firefox Accounts doesn't ride the Firefox trains, we're still applying a similar focus to squashing quality bugs in the leadup to Firefox 57. Our affectionately-named Crouton Flow <https://waffle.io/mozilla/fxa?milestone=FxA-130:%20Crouton%20Flow> backlog is the top of that priority list, and it's getting close to empty. - This cycle we fixed some weird egg-shaped profile pictures, made some Photon-inspired UX tweaks, eliminated some spurious authentication errors, and more. We also analyzed the results from two experiments that shipped in earlier trains: - On the Firefox first-run page, removing the greyed-out "disabled" treatment from incomplete forms results in a significant increase in both signups <https://sql.telemetry.mozilla.org/queries/28383#81380> and logins <https://sql.telemetry.mozilla.org/queries/28463#81450>. This was such a success that we're going to push ahead and roll out the change to all users. - Requiring users to confirm their password during account creation has given mixed results. It results in fewer signups <https://sql.telemetry.mozilla.org/queries/30926/source#82110> due to the increased friction, but the users that do sign up are less likely to reset their password <https://sql.telemetry.mozilla.org/queries/30926/source#82111> and hence more likely to have a good experience when connecting a second device. We're going to leave this experiment running for a while longer while we consider the trade-offs involved. As always, you can find more details in the changelogs for each repo: https://github.com/mozilla/fxa-auth-server/blob/v1.95.0/CHANGELOG.md https://github.com/mozilla/fxa-content-server/blob/v1.95.0/CHANGELOG.md https://github.com/mozilla/fxa-auth-db-mysql/blob/v1.95.0/CHANGELOG.md https://github.com/mozilla/fxa-basket-proxy/blob/v1.95.0/CHANGELOG.md Cheers, Ryan
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
