The latest articles on DEV Community by Luma Commons (@lumacommons). https://dev.to/lumacommons https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4145605%2Fea31e28c-e334-4419-8e64-2eee8c795205.jpg https://dev.to/lumacommons en Luma Commons Sun, 27 Sep 2026 14:40:56 +0000 https://dev.to/lumacommons/how-we-reduced-an-apps-crash-rate-from-2-to-01-3b3b https://dev.to/lumacommons/how-we-reduced-an-apps-crash-rate-from-2-to-01-3b3b <p>How We Reduced an App's Crash Rate from 2% to 0.1%</p> <p>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.</p> <p>We spent three months identifying the root causes and brought the crash rate down to 0.1%.</p> <p>The biggest issues weren't obvious bugs. They were:</p> <ul> <li>Core Data being accessed from multiple threads</li> <li>Memory pressure on older iPhones</li> <li>A third‑party analytics SDK that was leaking file handles</li> <li>Smaller issues around optionals, deep linking, and iOS edge cases</li> </ul> <p>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.</p> <p>The biggest lesson: you can't fix what you can't see.</p> <p>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.</p> <p>Read the full breakdown here:<br> <a href="https://www.lumacommons.com/blog/reducing-crash-rate-to-zero-point-one" rel="noopener noreferrer">https://www.lumacommons.com/blog/reducing-crash-rate-to-zero-point-one</a></p> ios mobile debugging swift