Firefox OS/Metrics: Difference between revisions
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
==Requirements== | ==Requirements== | ||
#Product Planning: Need to know the number of devices sold. This will help product decisions be data driven. | #Product Planning: Need to know the number of devices sold. This will help product decisions be data driven. | ||
# | #User Benefit: knowing the following information will improve security updates and app functionality | ||
## Build IDs, Country, Operator, OEM, Version of HW: These are needed for Device Updates and Security patches: When a bug is found, or a security risk is detected, they need to be sent as an update to the particular OEM, Operator. | ## Build IDs, Country, Operator, OEM, Version of HW: These are needed for Device Updates and Security patches: When a bug is found, or a security risk is detected, they need to be sent as an update to the particular OEM, Operator. | ||
##Screen Height, Width, Pixel density: This is needed for CoreApps development (Gallery, Camera, Dialer, Browser) and 3rd party apps. These apps need to know the screen sizes, resolutions that they would need to support. | ##Screen Height, Width, Pixel density: This is needed for CoreApps development (Gallery, Camera, Dialer, Browser) and 3rd party apps. These apps need to know the screen sizes, resolutions that they would need to support. | ||
==Design of Activation Ping== | ==Design of Activation Ping== | ||
#Activation Ping is triggered through the first-time use experience / activation. Will automatically retry until it is successful (on a 1 hour interval) | #Activation Ping is triggered through the first-time use experience / activation. Will automatically retry until it is successful (on a 1 hour interval) |
Revision as of 05:15, 28 March 2014
This is a placeholder page for design / discussion around Metrics in FxOS
Phase 1
Requirements
- Product Planning: Need to know the number of devices sold. This will help product decisions be data driven.
- User Benefit: knowing the following information will improve security updates and app functionality
- Build IDs, Country, Operator, OEM, Version of HW: These are needed for Device Updates and Security patches: When a bug is found, or a security risk is detected, they need to be sent as an update to the particular OEM, Operator.
- Screen Height, Width, Pixel density: This is needed for CoreApps development (Gallery, Camera, Dialer, Browser) and 3rd party apps. These apps need to know the screen sizes, resolutions that they would need to support.
Design of Activation Ping
- Activation Ping is triggered through the first-time use experience / activation. Will automatically retry until it is successful (on a 1 hour interval)
- Never pings again once it is successful (unless the phone's "userdata" partition is formatted through the recovery partition, but this is not a case we support generally, it means wiping all of the user's data)
- Can also be disabled, but requires extra work on top of disabling app updates or removing the Firefox marketplace app
Delta to what exists today
- Information:
- ActivationPing gives the total number of "sold"(activated) FFOS devices, whereas current ADI ping gives the devices connected to WiFi on a particular day
- Product planning needs the information about devices sold (ActivatioPing). Current ADI ping approximated devices active on a certain day on WiFi. Difference gives us an idea of retention of product, and engagement of user.. This will help us focus on what is causing the dropoff, investigate certain markets are doing better/worse, and making investments in improving the retention
- Activation Ping has additional information on Build IDs, Country, Operator, OEM, Version of HW, Screen Size, Screen Height, Width, Pixel density. While the previous ADI ping has model of device info.
- ActivationPing gives the total number of "sold"(activated) FFOS devices, whereas current ADI ping gives the devices connected to WiFi on a particular day
- Reliability:
- Current Ping from 1.3 shows approx 5 devices reporting as of March 24th 2014. https://dataviz.mozilla.org/views/ADI_Ping_1_3/HistoricalADITrend#2
- Cost:
- From previous versions, Partners removed ADI ping due to cost concern. Activation Ping is sent once in a lifetime, which should allay cost concerns.