Closed
Bug 969003
Opened 10 years ago
Closed 9 years ago
[Metrics Story] FxAccounts segmentations for UX
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: kparlante, Unassigned)
References
Details
User Story: As a UX designer, I want to know the context in which FxAccounts are used in practice, so that I can design UX appropriately for common devices' capabilities. Acceptance criteria: 1. UX designers have access to a dashboard showing them account creations per day, segmented by device, user agent, service, locale or screen size 2. UX designers have access to a dashboard showing them device attachments per day, segmented by device, user agent, service, locale or screen size 3. UX designers have information about device/user agent's capabilties in the common case (e.g. css3 and html5 availability) Timeframe: nice to have when the service first goes live
Reporter | ||
Updated•10 years ago
|
Component: Operations: Metrics/Monitoring → Server: Firefox Accounts
Summary: [Story] FxAccounts segmentations for UX → [Metrics Story] FxAccounts segmentations for UX
Reporter | ||
Comment 1•10 years ago
|
||
More info on segmentations: 1. locale - data available from request.summary log: https://github.com/mozilla/fxa-auth-server/pull/574 - locales: https://github.com/mozilla/fxa-content-server/tree/master/locale 2. screen size - not happening without support from client, so ignore for now 3. service & device (covered in https://bugzilla.mozilla.org/show_bug.cgi?id=968990) 4. other user agent related segmentations - split out OS as separate segment (at least for most common OS, the rest can be lumped in other) - split out Browser + version as separate segment (for at least most common browser/version combinations, the rest can be lumped into other) These segmentations are for slicing and dicing in kibana, they do not all need to be monitored in heka.
Reporter | ||
Comment 2•10 years ago
|
||
FWIW, these were the segmentations we used for Persona kpi dashboard: "OS": [ "Windows 8", "Windows 7", "Windows Vista", "Windows XP", "Macintosh", "Linux", "Android", "iOS", "FirefoxOS" ], "Browser": [ "Firefox", "Chrome", "MSIE", "Safari" ], Mappings: "Windows NT 6.2": "Windows 8", "Windows NT 6.1": "Windows 7", "Windows NT 6.0": "Windows Vista", "Windows NT 5.1": "Windows XP", "en" : "English", "es" : "Spanish", "pt-BR" : "Portuguese - Brazil", "de" : "German", "fr" : "French", "it" : "Italian", "pl" : "Polish", "tr" : "Turkish", "ru" : "Russian", "nl" : "Dutch",
Reporter | ||
Comment 3•10 years ago
|
||
FWIW, code that parsed the user agent string for Persona kpi dashboard: https://github.com/mozilla/persona/blob/dev/lib/coarse_user_agent_parser.js
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Comment 4•9 years ago
|
||
Unassigning myself from bugs that I'm not actively working on, & needsinfo rfkelly to triage. Set component to Metrics: Pipeline for any work requested from the data pipeline team (e.g. heka filters).
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(rfkelly)
Comment 5•9 years ago
|
||
I think this is old enough, and the landscape has changed enough, that we can open a new bug when we get around to revisiting this.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(rfkelly)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•