Explore 891 articles on Android performance
Showing 20 of 891 articles (Page 31 of 45)
Bumble's Android team slashed their ANR (Application Not Responding) rate by 6x. Here's how they debugged one of mobile's most frustrating problems.
Rob Pridham from BBC Sport reveals how his team tackled a massive Android refactor—migrating from multiple activities to a single-activity architecture while keeping the app running in production.
Rob Pridham from BBC Sport reveals how they modernized a 7-year-old Android codebase without a full rewrite. The secret? A strategic refactor that tackled navigation chaos first.
Rob Pridham from BBC Sport ditched the trendy frameworks and went old school—callback listeners and view controllers—to modernize their Android app. Controversial? Maybe. Effective? Absolutely.
Dropbox cut their Android CI pipeline from 75 minutes to 25 minutes without switching build systems. Here's how a team of 60+ mobile engineers solved testing at scale.
Grammarly's Android keyboard gets used 70+ times per day by the average user. Building it meant solving problems most app developers never face.
Fajar Ulin Nuha from Tokopedia reveals how their 50+ Android engineers manage a codebase that changes so dramatically every single week that assumptions become dangerous. Their solution? Become data-driven deve...
Hendry Setiadi from Tokopedia reveals how they built a custom logging system that catches production issues before users even notice. Firebase Crashlytics is great, but what if you need more?
Memory leaks are silent killers of Android app performance. They're hard to spot manually, but there's a tool that does the heavy lifting for you.
Gonçalo Alvarez from Farfetch drops a hard truth: 86% of users uninstall apps after one use due to poor performance. Your launch time might be costing you customers before they even see your product.
At Farfetch, a 0.1 second delay in warm app launch costs $4.2M annually. That's less time than it takes to blink.
Dropbox Android users couldn't see folders with Cyrillic characters or certain special names. The obvious fix? Way too risky to attempt.
Lyft's mobile apps used to poll a single endpoint every 5 seconds for everything. That "Universal Object" became their biggest reliability nightmare.
Pinterest's UI test suite was failing more than 50% of the time. Engineers were drowning in false positives, and tests had lost all credibility.
Microsoft Teams Android engineers faced a critical problem: heavy initialization code in lifecycle callbacks was killing app launch times. Their solution? Get lazy.
John Ryan from Flutter's team tackles one of mobile dev's messiest problems: navigation. But the solution might be more complex than the problem itself.
Eugene Zubkov from Revolut hit a wall building a custom Android chart: it literally disappeared due to texture size limits. His debugging journey reveals critical performance traps most Android devs don't see c...
Hesham Salman from GitHub reveals how GraphQL eliminated over-fetching and let their mobile team ship features at warp speed. The secret? Letting the client define exactly what data it needs.
Uber threw away years of code and rebuilt their rider app from scratch. Here's why that radical decision paid off.
Walmart's DevOps team has a bold claim: if you're not testing during development, you're risking the business. Here's why your testing strategy might be fundamentally broken.