Table of Contents
How Your Data Helps to Improve Firefox
The following slides are available in this presentation:
How Your Data Helps to Improve Firefox
Sending crash reports (and other info) pays off!
Program Manager, Mozilla QA
Slides: http://slides.kairo.at/fosdem2016/
- Created for Mozilla Developer Room at FOSDEM 2016 in Brussels.
- Written in HTML 5 with CSS 3 and JavaScript.
- Navigation via links on all slides, via access keys (e.g. "n"/Alt+Shift+N for "next") or back/forward arrow keys
- Contents
01/2016 Robert Kaiser -
"Mozilla", "Firefox" and their logos are
trademarks
of the Mozilla Foundation; Star Trek
and related items are trademarks of
Paramount Pictures.
Let's talk about Data
Data Privacy
Principles: mozilla.org/privacy/principles
- No surprises
- User control
- Limited data
- Sensible settings
- Defense in depth
Data Collection
- passive
- updates, blocklists, …
- active
- Telemetry, FHR, …
- Crash Reports, SSL Error reports, …
Crash Analysis
Finding new and rising crashes
Analyze crash data to help developers to debug and fix crash issues
Only voluntarily submitted crashes
Telemetry
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
Telemetry: Examples
Telemetry Experiments
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)
UI Telemetry
Telemetry about usage of UI elements
Example: items in toolbar vs. menu panel vs. customize mode
Android: dashboard, initial findings, url suggestions
Website A/B Testing
On Mozilla websites, classic A/B testing is being done.
Examples: Fundraising, many others
User Studies
with more invasive telemetry,
small set of users included
are informed and compensated.
Questions?