Hi All, Earlier today we had our weekly FxA demo session, and there's a recording available here:
https://vreplay.mozilla.com/replay/showRecordDetails.html?recId=4228 We had two-hand-a-half demos today: * Phil showed us his work on auto-generating API docs for the auth-server. We're currently keeping the API doc up-to-date by hand, which means it can easily get out of date, and means reviewers have to try to remember to check it's up to date. Phil's work parses a variety of source files to get information on error codes, parameters and validation, and takes a lot of the busywork out of keeping the doc up-to-date. * It's customized to the way we have code in auth-server, so it can be a bit brittle, but is also more capable than a generic code-to-docs generator would be. * It also leaves plenty of scope for hand-written content in and around the auto-generated bits, which is important for making docs that are easy to consume. * If we like it, we can consider running it automatically as part of the release-tagging procedure. * IIUC, it's already found one place where the existing doc had gotten out-of-date! * Vijay demoed the latest iteration of the "add secondary email" functionality, based on his collaboration with Ryan Feeley last week. There's now a single item in the settings page specifically for "secondary email", and the flow appears to work pretty smoothly. Some notes on the feedback: * The phrasing "secondary email address" might be a little confusing/unclear, but we haven't manage to come up with an alternative that doesn't over-promise. For example, "backup email address" is not really accurate because you can't use it to fully recover the account and all your sync data. * We'll need to iterate on the messaging to try to drive users to take advantage of this feature. * Our reliance on "refresh" buttons to keep the page up-to-date is not ideal UX and is a stop-gap; at some point we'll have to figure out an approach for sending real-time updates to the open page so that it's always up-to-date. * Plus some small follow-upchanges that I'm going to list at the end of this email so we don't lose track of them. * Ryan Feeley segued into showing us a proposed experiment for adding secondary emails directly in the sign-up flow, which you can see here: https://github.com/mozilla/fxa-content-server/issues/4811 There was broad support for trying out something like this, perhaps split into multiple smaller experiments. That's a wrap! Catch you next time. Ryan ----- Detailed follow-ups from the "add secondary email" demo: * There should be a separate error message for when you try to add your own primary email, versus an email owned by someone else. * The "refresh" button should remain active even after the user has added the secondary email. * Do we need a green success message for "Secondary email address removed"? * What's our metrics funnel for users who attempt to use this feature? * Do we have the ability to report unexpected attempts to add an email? * The artificial delay on the refresh button needs to be slower. * The question mark should be removed from "resend?" _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
