Hi Everyone,
As we wrap up the development cycle for FxA train-45, I wanted to take a moment to set the scene for work that's coming up in train-46. We've been working on getting all big chunks of work captured as features in aha and prioritized according to release here: https://mozilla.aha.io/products/FXA/feature_cards I hope this is becoming a more and more useful overview. Based on the above, we've got the following things in-flight to finish up in the next train: * Finalize reporting of metrics for single- vs multi-device users [1] * A couple of remaining email-quality issues [2] * Continuing work on backend service tokens [3] We've also got two important new features to ramp up work on, which I'll say a few words about individually: 1) Measuring user retention, and comparing it across different segments of users [4] This is going to be a key metric as we try various ways of improving the connected experience. We need to be able to tell if e.g. letting users customize their device setup inline in the signup flow encourages them to stick around in subsequent days. Ideally we will be able to generate graphs like [5] automatically and for different segments of users. I expect this will take multiple trains to complete. 2) Sending additional events to basket, for integration with the Journey Builder email system [6] The engagement team are launching an email "journey" to pitch opted-in users on the benefits of connecting multiple devices, which is really the key value proposition of sync. To make it go, their system needs to receive notifications when a user connects new devices to sync. This is not a *huge* feature in and of itself, but it's an excellent opportunity to revisit some of how the existing basket integration works, e.g. by factoring our "basket proxy" out into its own repository, and by moving SQS event handling responsibility over to it. So let's make the most of the refactoring opportunity and make space for doing it right. We'll also aim to to finalize our device-registration protocol [7] so we can get the backend components of it in place ahead of any client development in the Firefox 44 cycle. And finally, thanks to everyone who has been nominating important quality issues into "waffle:next", and let's make sure we make explicit time for some of [8] in the upcoming iteration. Thanks all! Ryan [1] https://waffle.io/mozilla/fxa?milestone=FxA-21:%20multi-device%20metrics [2] https://waffle.io/mozilla/fxa?milestone=FxA-29:%20email%20quality [3] https://waffle.io/mozilla/fxa?milestone=FxA-31:%20service%20tokens [4] https://waffle.io/mozilla/fxa?milestone=FxA-24:%20retention%20metrics [5] https://bugzilla.mozilla.org/show_bug.cgi?id=1173407#c36 [6] https://waffle.io/mozilla/fxa?milestone=FxA-44:%20journeybuilder%20events [7] https://waffle.io/mozilla/fxa?milestone=FxA-45:%20device%20registration [8] https://waffle.io/mozilla/fxa?milestone=FxA-0:%20quality _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
