We want to provide KPI data for Firefox Accounts on FirefoxOS. Establishing this as a meta bug, as I expect some of the data we want will be attainable server-side (e.g., successful sign-up completion rate), while other will require client-side code (duration of phases, etc.)
kparlante has produced this excellent etherpad for us to work out some high-level questions: https://id.etherpad.mozilla.org/fxacct-metrics
Here's the wiki describing Minimum Viable Metrics -- the metrics we need when FxA goes live (assuming FxOS/WMF/Marketplace are the first clients): https://wiki.mozilla.org/Identity/Firefox-Accounts/Minimum_Viable_Metrics
API proposal & fx-auth-server bug: https://github.com/mozilla/fxa-auth-server/issues/351
Tying this into 1.4, which I should have done some time ago. Katie at your convenience let me know what you might need from us.
Sam, for the basic use cases we're just observing calls to fxa-auth-server, so we shouldn't require much from the FxOS client code. To segment properly, it will help if the calls to the fx-auth-server have a "useful" user-agent (identifying FxOS + version). I'm not sure if this is already so, or if we should log an issue. FWIW, prioritized use cases: https://bugzilla.mozilla.org/show_bug.cgi?id=968973 (Accounts created per day) https://bugzilla.mozilla.org/show_bug.cgi?id=968983 (ADU) https://bugzilla.mozilla.org/show_bug.cgi?id=968990 (Device, service segmentations) https://bugzilla.mozilla.org/show_bug.cgi?id=969007 (UX flow drop off) FxOS specific use cases (we should talk about priority, may require extra work/creativity): https://bugzilla.mozilla.org/show_bug.cgi?id=969025 (Add email verification stage) https://bugzilla.mozilla.org/show_bug.cgi?id=969029 (%skip FxA create at FTU) Not currently prioritized (will require information from the client, either passed in on fxa-auth-server calls, or from separate telemetry): https://bugzilla.mozilla.org/show_bug.cgi?id=969010 (UX timing visualizations) In other words, the API changes proposed in the github issue listed above (351) have not yet been implemented -- for now I'm assuming the standard onepw API as documented and (hoping for?) a meaningful user agent.
Katie -- thanks very much. Here's the user-agent as of today's m-c xpcshell tests: Mozilla/5.0 (Mobile; rv:30.0) Gecko/20100101 Firefox/30.0 Maybe we can chat with Adam and Tauni about the best way to add this work to the (very long) queue for 1.4.
Moving to Core::FxAccounts for further triage; since it's two years old I suspect we can just close it, unless anyone on the bug objects?
Component: Identity → FxAccounts
Firefox OS has given up the ghost.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.