26 articles on App Stability for iOS performance
Showing 20 of 26 articles (Page 1 of 2)
Chamod Lakmal shares how discovering hundreds of weekend crashes on Monday morning pushed him to build an automated alert system. No more silent failures destroying your app's reputation while you're offline.
Half of all users uninstall an app after a single performance issue. A peer-reviewed paper puts specific numbers on the thresholds that separate apps people keep from apps they delete.
Phil Niedertscheider from Sentry reverse-engineered Apple's private frameworks after iPadOS 26 broke a fundamental assumption: that successful type casts guarantee the object is actually that type.
Alastair Houghton from Apple's Swift runtime team just dropped a game-changer for debugging: Swift 5.9 now catches crashes and lets you inspect them interactively before your program dies.
Uber deploys 11,000 code changes weekly. How do they catch crashes before users notice? They built Healthline, powered by Apache Pinot.
Grab's engineering team faced a brutal problem: rain in Southeast Asia would crash their entire ride-hailing system. When demand spiked locally, users everywhere suffered.
Meta's Engineering blog just hit a 404. Sometimes even the biggest tech companies deal with broken links and content migrations.
Turo's iOS team took their crash-free rate from 99% to 99.99% in just one year. Here's how a lean 5-engineer team achieved what most would consider impossible.
Lyft engineers faced a nightmare scenario: feature flags causing infinite crash loops on app launch, requiring emergency hotfixes and losing revenue. They built Safe Mode to break the cycle.
Robinhood eliminated 30% of ALL iOS crashes by refactoring a single screen. That screen drove 30% of their revenue at the time.
Lyft was serving 17.1M riders while their Android app launched 15-20% slower than competitors. Time to fix that.
Revolut built a system that automatically blocks code deployments based on security risk and bug count. Here's how they shifted security left without slowing down 165,000+ pull requests.
Grab lost 95% of ride bookings for a full minute when a single Redis slave node failed. Their highly available cluster with multiple replicas somehow became a single point of failure.
Grab's logging bills were spiraling out of control. Their solution? A complete rethink of how they capture what happens in production.
Cash App open sourced a tool that solves one of iOS debugging's most frustrating problems: crashes that you can't reproduce locally.
Shopify's iOS team ships hundreds of commits weekly to a monorepo. Their testing strategy keeps quality high without slowing down velocity.
LinkedIn processes massive volumes of mobile crash data to keep their app stable for millions of users. Here's how they built the pipeline.
LinkedIn built their own crash reporting system instead of using third-party tools. Here's why that decision paid off.
Etsy built Crashcan, their own mobile crash analytics layer on top of a third-party provider. Why not just use the vendor's dashboard?
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.