Explore 891 articles on Android performance
Showing 20 of 891 articles (Page 20 of 45)
Instagram's app was getting bloated. More engineers, more features, slower cold starts, and ballooning app size threatened the lean experience users loved.
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?
ShareChat cut janky frames by 75% and boosted feed scrolling by 60%. Here's how they debugged their way to a 4.3-star rating.
Swiggy's mobile team faced a common problem: juggling disk caches, LRU caches, and databases without creating a maintenance nightmare. Here's their elegant solution.
Lazar Nikolov from Sentry explores Jetpack Compose, Google's declarative UI toolkit that's already powering 160 of the top 1,000 Android apps. If you're still building with XML Views, this deep dive shows what ...
Jyoti Sheoran breaks down MVI architecture with a complete Jetpack Compose implementation that actually makes sense. No theory overload, just practical code you can use today.
BAM just launched Flashlight, a Lighthouse-inspired tool that finally brings performance scoring to mobile apps. Android developers now have a standardized way to measure app performance.
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.
Swiggy's Android team was stuck in a painful cycle: rebasing PRs, waiting hours for full test suites to run, then doing it all over again. One frustrated engineer decided to fix it over a weekend.
Lyft discovered memory leaks affecting only 1% of users—issues that would never show up in local testing. Here's how they built a production monitoring system to catch what profiling tools miss.
Here's a performance optimization problem most Android teams don't see coming: your security tooling might be silently breaking your baseline profiles. Guardsquare just solved it.
Syntia from Blibli.com tackles one of Jetpack Compose's most frustrating gotchas: the dreaded nested scroll crash. If you've ever hit that 'infinity maximum height constraints' error, this one's for you.
Roger Hu from Square reveals how Android Studio Electric Eel slashed their sync times by 60%. For a team managing 3,000+ Gradle subprojects, that's not just faster—it's 1,600 hours of developer time saved annua...
Animations can make or break your app's performance. Choosing between Lottie and Rive isn't just about features: it's about understanding the tradeoffs that impact your users' experience.
The article link appears to be broken or unavailable. I cannot access the content about GoTransit's mobility integration.
Delivery Hero was burning through 9TB of image data daily. Their apps were sluggish, their network costs were astronomical, and users were waiting too long for images to load.
Strava's Android team hit a wall: testing server-driven UI meant wrestling with Charles Proxy crashes, EOF errors, and 3-4 minute build times. An intern decided to fix it.
OkCredit reduced frozen frames by 40% by obsessing over a metric most Android teams ignore: screen response time.
Swiggy's search feature was a mess: 2,000+ lines in a single ViewModel, monolithic XML files, and performance issues. Time for a complete rewrite.
Paul Hundal from Square's Mobile Developer Experience team reveals how one Gradle feature saved their Android team the equivalent of watching 60 football games worth of waiting time. The ROI? $1.1 million annua...