Definition
The percentage of user sessions or app launches that end in an unexpected crash or critical error, measured by the app store or in-app analytics.
Why It Matters for ASO
Crash rate directly impacts app store visibility and user retention—two critical ASO metrics. Apps with high crash rates trigger negative reviews and uninstalls, damaging App Store rankings and algorithmic visibility. Major app stores consider stability in ranking signals, often limiting featured placements or recommending unstable apps less frequently. A single version with widespread crashes can reset months of optimization work.
Key Points
- Industry standard threshold is <1% crash rate; above 2% significantly impacts rankings and user acquisition
- Each crash generates user frustration and typically results in a negative review, compounding ASO damage
- Platform-specific measurement: iOS reports unified crash rate; Android separately tracks ANRs (Application Not Responding)
- Crash spikes should trigger immediate investigation and rollback—prolonged high rates can trigger algorithmic suppression
- Emerging markets experience higher rates due to device/network fragmentation; requires geographic testing and monitoring
- Crashes are often device or OS version-specific; segment analysis identifies patterns and platform priorities
- Pre-release testing on real devices reduces post-launch discovery and user impact