Mobile/Metrics
< Mobile
Jump to navigation
Jump to search
This page explains the different tools available to analyze data about how people use Firefox for Android.
Note: some metrics are only available to employees and may require sign-in.
Usage Metrics
Dashboards
- Adjust: Third-party SDK initially added to track install referrers, but currently our most trusted source of usage numbers. Also used to track retention.
- ADI dashboard: Gives us more granular daily use numbers per release version. Very old way of collecting usage numbers, based off blocklist pings.
- Executive metrics: Mostly not useful since we removed FHR.
Telemetry
Our telemetry systems are currently in flux, but we are working towards a unified telemetry data pipeline to measure sessions and events. We have two levels of telemetry, opt-out and opt-in, which are controlled by data sharing preferences in our settings UI. Opt-in telemetry is enabled by default up to beta, but is really opt-in on release.
- Telemetry docs: Some of this is used on both desktop and Android, but some of it is specific to desktop only. Use caution when reading these docs in a mobile context.
- re:dash via SQL: Handy tool for performing analysis against telemetry data. Right now this only includes opt-in telemetry data.
- Self-serve telemetry analysis: Older, more hardcore tool for doing telemetry analysis.
- UI telemetry: Mobile-specific UI telemetry implementation. You can query this data with re:dash, or look at the UI telemetry dashboard.
- Core ping: New opt-out telemetry ping that we're working on to replace FHR.
- Histogram dashboard: Histogram probes are used mostly for engineering metrics. They are not as useful for product decisions, and we may stop sending histogram telemetry data on mobile.
Stability and Performance
Dashboards
- Crash stats: Where we monitor crashes.
- Perfherder: Charts to monitor memory use, build times, and APK size.
- Autophone: Startup performance tests.