Explore 937 articles on Android performance
Showing 20 of 937 articles (Page 27 of 47)
Sahil Jain from OLX reveals how they manage multiple market versions of their Android app without maintaining separate codebases. The secret? Strategic use of Gradle's build configuration.
LazyPay was serving unoptimized images directly from S3, killing app performance and burning bandwidth. Their migration to Cloudinary cut image sizes by 70%.
ClassPass engineers were hitting a wall: their Jersey-based APIs couldn't handle traffic spikes without exhausting thread pools. The culprit? Synchronous request processing blocking precious I/O threads.
Robinhood was taking weeks and multiple engineers just to make simple UI changes. Their solution? Server-Driven UI that lets them ship to all platforms without app releases.
Tokopedia cut their Android app download size by 10% using Dynamic Features. But the implementation wasn't as simple as Google's docs suggested.
Zomato's Android team breaks down SSL certificate pinning: the security feature that could brick your app if done wrong.
Uber rewrote their Android rider app in 2016 and made an architectural choice that most Android teams avoid: deeply nested dependency injection scopes.
Zomato's Android team is tackling a critical vulnerability that most apps ignore. Your encrypted HTTPS traffic might not be as secure as you think.
Ju Cai from Coupang reveals how their Android app went from Stone Age message passing to a custom LiveData-based event bus that cut development time in half. The journey through three architectural eras offers ...
Slack just wrapped a massive mobile refactor. The results? 68% of iOS and 92% of Android codebases modernized, with CI times slashed by over 60%.
Slack's mobile codebase was slowing teams down. Their solution? Break the monolith into hundreds of independent modules.
Alexandre Bruneau from Medium Engineering discovered that Jetpack Compose's elevation overlay only works with default Material theme colors. His workaround unlocks custom color elevation for any design system.
DoorDash makes millions of ML predictions per second, but their Redis-based feature store was becoming a massive cost and scalability bottleneck. Could client-side caching be the answer?
Slack's engineering team ran into a classic performance testing problem: spinning up load tests was so time-consuming that teams avoided doing it. Their solution? Never stop testing.
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.
Swiggy's mobile team was drowning in Jenkins bottlenecks. Build times were slow, machines crashed frequently, and manual interventions killed velocity.
Tokopedia's iOS team was drowning in 30-minute unit test cycles with 65 developers fighting over 9 CI/CD machines. They cut that time by 8X.
Lyft's Android app serves millions of users daily, but how do you track CPU performance when hundreds of engineers ship code constantly? The team built a custom monitoring system from scratch.
Phil Boyd from OkCupid shows how to build smooth path animations in Jetpack Compose using just high school math. No complex animation libraries required.
Grab's engineering team just unlocked 30% memory savings and 38% storage reduction with a simple compiler flag. Here's how Profile-Guided Optimization (PGO) delivered massive gains with minimal code changes.