Discover 47 articles on App Stability in mobile performance
Showing 7 of 47 articles (Page 3 of 3)
An Allegro engineer spent weeks hunting a MapKit bug so elusive it disappeared and reappeared randomly across devices. The investigation went from Swift code to assembly to a conversation in San Francisco.
LinkedIn's iOS team set an audacious goal: ship to production three times daily, with just three hours from commit to release. Here's how they actually pulled it off.
Skyscanner's test suite had a 99% pass rate. Sounds great, right? Wrong. Those false failures were costing hours of productivity and masking real production issues.
Meta's iOS team faced a silent killer: crashes that left no trace, no stack trace, no clue. Just frustrated users and a mystery to solve.
Duolingo shipped their first Swift app in 2015 and achieved a 0.2% crash rate. Here's what they learned building a high-stakes testing app where crashes cost users real money.
Etsy's iOS team faced a dilemma: their safety net for preventing crashes was quietly hiding logic bugs across the entire codebase.
Twitter's iOS team shipped beta builds to employees and discovered crashes that would never show up in testing. The culprit? Jailbroken devices and unprefixed Objective-C categories.