How We Reduced an App's Crash Rate from 2% to 0.1%
A 2% crash rate meant roughly 8,000 user sessions were ending in a crash every month for a retail banking app serving around 400,000 monthly active users.
We spent three months identifying the root causes and brought the crash rate down to 0.1%.
The biggest issues weren't obvious bugs. They were:
- Core Data being accessed from multiple threads
- Memory pressure on older iPhones
- A third‑party analytics SDK that was leaking file handles
- Smaller issues around optionals, deep linking, and iOS edge cases
Before fixing any of these, we first fixed the crash reporting and monitoring setup. Once we had reliable data, we could identify patterns instead of guessing.
The biggest lesson: you can't fix what you can't see.
We also added ongoing monitoring for crash rates, memory usage, release performance, and recurring crash signatures so stability wouldn't degrade again as the product evolved.
Read the full breakdown here:
https://www.lumacommons.com/blog/reducing-crash-rate-to-zero-point-one
Top comments (0)