Program Management/Programs/Telemetry/Improve Opt-in: Difference between revisions
(→Mobile) |
|||
| Line 20: | Line 20: | ||
The following are some tactics that may be used to increase the opt-in rate for Telemetry. | The following are some tactics that may be used to increase the opt-in rate for Telemetry. | ||
==Change to opt-out policy== | ==Change to opt-out policy on Aurora and Nightly== | ||
Will change to opt-out (enabled by default) on Aurora and Nightly channels. See {{bug|699806}} Enable Telemetry by default on Nightly and Aurora channels | |||
<bugzilla> | |||
{ | |||
"id": "699806,702284,728340,728350,701182,723129,725407,725987" | |||
Will change to opt-out (enabled by default) on Nightly | } | ||
</bugzilla> | |||
==Change opt-in ui== | ==Change opt-in ui== | ||
Revision as of 16:53, 28 February 2012
Goal
It is thought that the current Telemetry opt-in rates do not provide enough data to be useful. In general, Telemetry is only useful if users are providing feedback. The issue with Telemetry data lies in the sample population. Because Telemetry is opt-in, the sample population is not random and therefore needs to be very large (80-90%) to answer a broad range of questions. It may still be possible to answer specific questions with a smaller sample size (metrics can engage on an ongoing basis to assist with determination of whether a question can be answered). Alternatively, the existing sample population may contain enough variety to be representative.
Investigation
The metrics team (Chris Jung) will investigate to see if the current Telemetry data is representative based on the information that we have available from daily add-on pings. See bug 698848.
Lawrence will investigate changing Telemetry to an opt-out option.
Release and Beta channels
Current: ~2%
Goal:
Nightly (M-C) and Aurora channels
Current: ~2%
Goal: ~100%
Nightly and Aurora have small user bases when compared with Beta and Aurora. It is important to have as close to full adoption as possible in order to obtain meaningful data. Note that the users on these channels are assumed to be more technically savvy and interested in contributing to the improvement of Firefox.
Tactics
The following are some tactics that may be used to increase the opt-in rate for Telemetry.
Change to opt-out policy on Aurora and Nightly
Will change to opt-out (enabled by default) on Aurora and Nightly channels. See bug 699806 Enable Telemetry by default on Nightly and Aurora channels
8 Total; 0 Open (0%); 7 Resolved (87.5%); 1 Verified (12.5%);
Change opt-in ui
Desktop
Issues with the current opt-in UI:
- UI may disappear quickly
- UI may be hidden in another tab
These issues are related to the prompt mechanism (used for know your rights message) not being designed to be used heavily.
Bugs:
- Replace opt-in UI bug 692861 - Need to discuss UX goal
- Current UI gets dismissed too easily
bug 691951- Fixed in Firefox 9 - Telemetry prompt should be tri-state
bug 697860- Fixed in Firefox 9 - Enable Telemetry by default on nightly and Aurora bug 699806
Want to pursue a more aggressive opt-in UI for nightly. Suggestion in bug 683340 (incomplete and needs UX design). Another suggestion is to put a checkbox on the download page (like Chrome) but this has two notable drawbacks: Firefox is multiseat and this only addresses new downloads not updates.
Follow up with:
- UX
- Brian Dils is engaged and looking at the current notification mechanism. Lawrence and Brian will sync up at the mobile work week (Oct. 17-21)
Mobile
- Need to add a Telmetry preference for Fennec Native UI
bug 696076 - Need to advertise Telmetry on mobile
bug 699513 - Telemetry on mobile should be tri state bug 702281
- Enable Telemetry by default on nightly and aurora bug 699806
Increase publicity
Using the Mozilla blog (others?) promote Telemetry and request user help with improving the performance of Firefox.