Explore 891 articles on Android performance
Showing 20 of 891 articles (Page 24 of 45)
Alexander Dadukin and Dhriti Chawla reveal what it's like being the only 2 Android engineers supporting analytics infrastructure for all of Yelp. Spoiler: they can't see or touch what they build.
Gojek runs 15,000+ VMs across 250+ GCP projects serving millions of customers. How do they manage infrastructure at this scale without chaos?
OkCredit serves millions in India's Tier-2/3 cities where flaky networks are the norm. Their Android team just cut network call times by 30% with some clever client-side optimizations.
Klarna's team removed their caching layer and saw a 25% performance boost. Wait, what?
Turo's Android team hit a wall: their single-device test setup couldn't keep up with their growing UI test suite. Hours of wait time for a single test run wasn't going to cut it.
Swiggy was drowning in analytics chaos. Thousands of events per session, scattered specs across docs, and manual verification eating up engineering time.
Johnson Li from Coupang reveals how migrating from Mac minis to AWS EC2 transformed their mobile CI/CD pipeline. Their team was drowning in 3,000+ daily builds with 1-hour wait times.
React Native just made a massive default change that could speed up your app launches and shrink your bundle size. Here's what the benchmarks show.
Mercado Libre's Android team achieved a 24% performance boost without using Google's recommended Baseline Profiles or Macrobenchmark tools. How did they pull it off?
Booking.com's Android team built their own rendering performance monitoring system. Here's why Google Play Console metrics weren't enough.
Neil Davies from Just Eat Takeaway reveals how his team eliminated manual theme updates across multiple Android apps. Their solution? A design token system that cut redesign time by 80%.
Tinder was manually creating 40+ localized Lottie animations for every campaign. Their solution? A clever architecture that reduced it to just one.
Very Good Ventures shows how to build a production-ready Flutter app with Supabase that achieves 100% test coverage. This isn't your typical Firebase clone tutorial.
OkCredit slashed their Android app cold startup time by 70%. Here's the engineering playbook that made it happen.
Mercado Libre's mobile apps serve 4.5 billion active devices. A Galaxy A10 might take 5 seconds to load a screen—or just 1.67 seconds, depending on conditions.
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%.
Tokopedia cut their Android app download size by 10% using Dynamic Features. But the implementation wasn't as simple as Google's docs suggested.
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.
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.