canmove, Confirmed users
312
edits
Firefox OS/Metrics: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
=FTU ping= | =FTU ping= | ||
==Design of Activation Ping== | |||
#Activation Ping is triggered through the first-time use experience / activation. | |||
#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 | |||
==Details== | |||
When a device is first activated, The FTU ping service sends a simple one-off HTTP request to our telemetry server. The HTTP request contains a JSON payload with some high level information about the device and network, but no unique hardware identifiers. A randomly generated pingID is sent to help with filtering on the server side, but this ID is discarded by the server once filtering has occurred (generally after 24 hours). | When a device is first activated, The FTU ping service sends a simple one-off HTTP request to our telemetry server. The HTTP request contains a JSON payload with some high level information about the device and network, but no unique hardware identifiers. A randomly generated pingID is sent to help with filtering on the server side, but this ID is discarded by the server once filtering has occurred (generally after 24 hours). | ||
| Line 55: | Line 59: | ||
* Change <tt>DEFAULT_TRY_INTERVAL</tt> in <tt>gaia/apps/system/js/ftu_ping.js</tt> to something much smaller than 1 hour (i.e. 15 seconds) | * Change <tt>DEFAULT_TRY_INTERVAL</tt> in <tt>gaia/apps/system/js/ftu_ping.js</tt> to something much smaller than 1 hour (i.e. 15 seconds) | ||
= | =High Level 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 | #User Benefit: knowing the following information will improve security updates and app functionality | ||
| Line 62: | Line 65: | ||
##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. | ||
==Delta to what exists today== | ==Delta to what exists today== | ||
#Information: | #Information: | ||