Explore 937 articles on Android performance
Showing 20 of 937 articles (Page 33 of 47)
Phill Williams and Vijay Gondi from Netflix reveal how a codec upgrade is solving one of mobile streaming's most annoying problems: constantly adjusting your volume.
Snap's engineering team obsesses over one metric: Time to Camera Ready. Miss the bear crossing the street because your app was too slow? That's exactly the problem they're solving.
Rico Harisin from Tokopedia reveals how their Android team shipped weekly releases while building a complete performance infrastructure from scratch. Their secret? Treating CI/CD like a product.
Emily Fujimoto from Thumbtack reveals how her team caught critical layout bugs that traditional testing completely missed. The solution? Screenshot tests that verify what your UI actually looks like, not just w...
Jingwei Hao from Lyft reveals how real-time stats APIs caught a production crash spike at 9:55am, enabling engineers to ship a hotfix before most users even noticed the problem.
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.
Bumble's Android app was bleeding users to ANR dialogs. Their ANR rate sat above Google Play's threshold, threatening search rankings and user trust.
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.
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?
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...
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.
At Farfetch, a 0.1 second delay in warm app launch costs $4.2M annually. That's less time than it takes to blink.
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.
Lyft's mobile apps used to poll a single endpoint every 5 seconds for everything. That "Universal Object" became their biggest reliability nightmare.
Dropbox Android users couldn't see folders with Cyrillic characters or certain special names. The obvious fix? Way too risky to attempt.
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.