How Your Data Helps to Improve Firefox
Sending crash reports (and other info) pays off!
Program Manager, Mozilla QA
Let's talk about Data
- Telemetry, FHR, …
- Crash Reports, SSL Error reports, …
Finding new and rising crashes
Analyze crash data to help developers to debug and fix crash issues
Only voluntarily submitted crashes
Anonymized data from very specific probes, e.g. startup time, crashes experienced, number of bookmarks, etc.
Environment, e.g. OS, graphics hardware and drivers, add-ons, etc.
2 sets of data: base (formerly FHR) + extended
Dashboards & Documentation: telemetry.mozilla.org
On pre-release channels, A/B test shipped to specific set/percentage of users, control plus experiment groups
Examples: e10s (right now), default search (late 2014)
Website A/B Testing
On Mozilla websites, classic A/B testing is being done.
Examples: Fundraising, many others
Focused studies done at times,
with more invasive telemetry,
small set of users included
are informed and compensated.