By Abdelrahman Saed — Lead Mobile Engineer. Last updated: 2026-08-10.
Crash-free rate is the percentage of app sessions that end without a crash. It is the single most important mobile quality metric — it directly measures user experience. A rate of 99.9% means fewer than 1 in 1,000 sessions crash. Industry benchmark: 99.5%+ is acceptable; 99.9%+ is excellent.
Crash monitoring tools (Sentry, Firebase Crashlytics, Bugsnag) instrument the app to capture unhandled exceptions and native crashes:
Crash-free rate = (total sessions - crash sessions) / total sessions × 100
A "session" starts when the app launches and ends when the user closes it or it crashes. A single user can have many sessions per day.
At iStoria (5M+ users, 350+ releases), we hold 99.9% crash-free across every release. How:
Either<Failure, T>, so error paths are explicit forks the UI renders, not unhandled exceptions that crash the app.Every production app should track crash-free rate. There is no "when not to" — it is a baseline quality metric.
Target benchmarks:
99.5%+ is good, 99.9%+ is excellent. At iStoria (5M+ users), we hold 99.9% — fewer than 1 in 1,000 sessions crash. Anything below 99% is a red flag that needs immediate attention.
Both are excellent. Sentry has superior Dart stack traces and is better for Flutter. Firebase Crashlytics is better integrated with the Firebase ecosystem. At iStoria, we use Sentry. See our Sentry vs Firebase Crashlytics comparison.
Available for hire. Abdelrahman Saed is a Lead Mobile Engineer (Flutter) — open to full-time, fractional, contract, or advisory work. Hire me →
Book a 20-minute call · Download the CV (PDF) · See how I work