Discover 47 articles on App Stability in mobile performance
Showing 20 of 47 articles (Page 1 of 3)
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.
SBI serves 80 million users on Flutter. Nubank has 100 million. BMW runs it in 47 countries. Here's the full list.
Luca from Mercari's Logistics team hit a wall: multiple ViewModels on one screen needed to share data, but Hilt's built-in scopes forced them into Singleton hell with manual cleanup. So they built their own sco...
JioHotstar pushed their Android app from 99.5% to 99.8% crash-free rate by hunting down invisible memory killers. Here's how they did it.
Google's Android team just dropped a performance framework that meets you where you are. Whether you're a solo dev or leading a performance team, there's a clear path forward.
Ben Weiss from Google shares how Reddit achieved 40% faster cold startup and boosted Play Store ratings in under 2 weeks. The secret? Finally enabling R8 optimizer's full potential.
Your Jetpack Compose app might be recomposing 10X more than it needs to. The culprit? Stability.
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.
Mohomed Nawab reveals how QA became the unsung hero in PickMe's driver app overhaul. Most teams treat testing as a final checkpoint, but this approach flipped the script entirely.
Andrew Tunall, President of Embrace, makes a bold claim: your app's biggest retention killer isn't crashes. It's the performance issues you're not even tracking.
Your Android app might be bleeding users before they even finish launching it. Performance isn't a feature anymore. It's table stakes.
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.
Tracy Stampfli from Slack reveals how her infrastructure team keeps 120+ mobile engineers shipping features without breaking the app. The secret? Treating mobile connectivity like a first-class problem, not an ...
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.
A single character in a Gradle config file took down Android builds for every React Native version simultaneously. Here's how the React Native team handled a 4-day global outage.
Meta tackled the billion-dollar mistake: NullPointerExceptions causing 27% of their Android crashes. Here's how they retrofitted null-safety onto millions of lines of Java without rewriting everything.
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.
Swiggy discovered 8% of their delivery drivers were running cloned apps and spoofing GPS locations. This was breaking their live order tracking system and creating chaos for customers.