Explore 891 articles on Android performance
Showing 20 of 891 articles (Page 27 of 45)
Airbnb ditched single-metric performance tracking and built something better. Here's how they unified web, iOS, and Android performance into one 0-100 score.
Patrick Brochado from BlaBlaCar turned a 13-minute Android build into a 4-minute one. His team was losing 8 hours of productivity every single day to slow builds.
Facebook's Android app serves 2.9 billion users monthly. Their startup optimization strategy cut bad starts by focusing on one counterintuitive metric.
Cash App's Jake Wharton just open-sourced their solution to a problem every mobile team faces: state management code that's impossible to read.
Sonic Wang from DoorDash breaks down Kotlin coroutines from bytecode to scheduler. If you've ever wondered what actually happens when you call 'suspend', this deep dive reveals the magic.
Ryan O'Neill from Square reveals why 9 out of 10 mobile shoppers think their experience could be better. His team's solution? Stop thinking mobile-first and start thinking app-first.
Lyft was serving 17.1M riders while their Android app launched 15-20% slower than competitors. Time to fix that.
Anisha Inas Izdihar and Yusuf Cahyo Nugroho from Traveloka cut build times by 37% and saved users 15MB of storage. Here's how they migrated 26 modules to Android's Dynamic Feature Module framework.
Meta's Hermes team cut app startup time in half and reduced GC pauses by 34x. Here's how they're making it the default engine for React Native.
Jintin from Carousell reveals how a 3,000+ line Presenter became their team's productivity nightmare. Their solution? A strategic mix of refactoring AND rewriting that didn't require months of downtime.
Buğra Yetkin from Teknasyon Engineering breaks down why Android teams are ditching XML and fragments for Jetpack Compose. The promise? Less code, better performance, and a completely new way of thinking about U...
Doist went from scary 2-hour manual Android releases to shipping every single day. Here's the engineering playbook that made it possible.
DoorDash's Android team learned the hard way that adding payments isn't just about processing transactions. It's about building a system that scales across countries, payment methods, and user expectations.
Victor Oliveira from Mercado Libre reveals a harsh truth: 53% of users uninstall apps due to performance issues. With 4.5 billion active Android and iOS devices worldwide, each performing differently, mobile pe...
Mallika Potter and Kevin Beaulieu from Thumbtack reveal how they open-sourced their entire native design system—and the surprising technical challenges they had to solve first.
Doni Winata from Traveloka's Android Infra team reveals why constantly increasing Gradle's heap size actually makes your build problems worse. His deep dive into Android build memory issues shows how to stop fi...
Grab's engineering team learned the hard way: retries and circuit breakers aren't enough when you're running hundreds of microservices at scale.
Walmart's engineering team learned the hard way: breaking up a monolith without fixing team structure just creates a distributed mess.
Revolut built a system that automatically blocks code deployments based on security risk and bug count. Here's how they shifted security left without slowing down 165,000+ pull requests.
Tokopedia built an internal tool that automatically finds Android performance bottlenecks. No more manual trace analysis or guessing which methods are slowing you down.