Quick answer: Crash count is misleading without play time context. MTBF (mean time between failures) normalizes for play patterns; trends are meaningful.
100 crashes from 1000 sessions vs 100 crashes from 10,000 sessions. Same count; different quality. MTBF clarifies.
Compute MTBF
Total play time / total crashes. Per-build; per-platform.
Track over releases
MTBF should rise. Regressions are visible.
Per-system MTBF
Combat MTBF; UI MTBF. Drills down to system-level quality.
Target an MTBF budget
'Average player should crash less than once per 4 hours'. Concrete; verifiable.
“MTBF is the quality metric players experience. Track it.”
Crash counts impress; MTBF informs. Move your dashboards to the second.