Firefox OS/Metrics

This is a placeholder page for design / discussion around Metrics in FxOS

Phase 1

Requirements

For User Benefit, knowing the following information will security updates and app functionality

1. 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.
2. 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

1. Is triggered through the first-time use experience / activation. Will automatically retry until it is successful (on a 1 hour interval)
2. 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)
3. 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

1. Information:
   1. ActivationPing Gives the total number of "sold"(activated) FFOS devices, whereas current ADI ping gives the devices connected to WiFi on a particular day
      1. Product decision making needs the information about devices sold (ActivatioPing). Current ADI ping approximated devices active on a certain day on WiFi. Difference is retention. This will help determine focus on what is causing the dropoff, investigate certain markets are doing better, and making investments in improving the retention
2. Reliability
   1. 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
   2. From previous versions, Partners removed ADI ping due to cost concern. Activation Ping is sent once in a lifetime, which should allay cost concerns.