32 articles on App Stability for Android performance
Showing 20 of 32 articles (Page 1 of 2)
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.
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.
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.
Your Android app might be bleeding users before they even finish launching it. Performance isn't a feature anymore. It's table stakes.
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.
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.
Strava thought they had a few hundred crashes per day. Crashlytics revealed they were missing 42,000 crashes per week.
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.
Etsy was getting 1,000 Out of Memory crashes per day on Android. The culprit? A navigation architecture from 2012 that couldn't handle modern browsing behavior.
Tokopedia shipped Android App Bundles and immediately hit a wall: mystery crashes on random devices. The culprit? Sideloaded APKs missing critical resources.
Lyft was serving 17.1M riders while their Android app launched 15-20% slower than competitors. Time to fix that.