Explore 926 articles on Android performance
Showing 20 of 926 articles (Page 25 of 47)
Mehmet Gür from Getir tackles a common Android pain point: uploading files to S3 with real-time progress tracking. His solution avoids the MultipartBody pitfalls that trip up most developers.
OkCredit ran a fascinating A/B test: Jetpack Compose vs XML layouts in production. The results surprised them—and reveal what most teams miss about Compose performance.
Instawork runs over 1 million tests daily in their CI pipeline. Here's how they made unit testing a core engineering practice, not an afterthought.
Turo's Android team faced a challenge: how to adopt Jetpack Compose without rewriting their entire fragment-based app overnight.
Meetup's Android team ditched Activities and Fragments for pure Jetpack Compose—and immediately noticed the performance difference. Here's how they navigated the complexity of multi-module apps.
Zomato's Android team was losing 7 hours of productivity every single day just waiting for builds. A 10-person team, 20 builds per day, 2+ minutes each time. The math was brutal.
Uber built a web app that loads in 3 seconds on 2G networks. Here's how they made it smaller than a typical image file.
Tinder adopted Jetpack Compose before it hit 1.0. Here's how they navigated the alpha/beta chaos in a massive production app.
Andrey Kovalev from Bumble's engineering team challenges a fundamental assumption: what if Jetpack Compose Navigation's string-based routes and hardcoded BackStack are holding your Android app back?
Sid Patil from Delivery Hero shares how his team turned Droidcon Berlin into a masterclass on scaling Android apps across 50 countries. Over 300 developers stopped by their booth to learn what it takes to build...
Pinterest was bleeding user engagement on Android. With 75% of signups coming from outside the U.S. and 90% of global smartphones running Android, they had to fix their performance problem fast.
Strava's Android team hit a wall trying to modularize their codebase the traditional way. So they flipped their entire architecture upside down.
Grab's engineering team discovered their Go apps were mysteriously throttling at 1.94 CPU cores but flying at 2 cores. The culprit? A sneaky interaction between Kubernetes VPA and GOMAXPROCS.
Seongchul Park from Coupang reveals how they tamed a 300,000+ line monolithic Android codebase. The build times were spiraling, new features were getting tangled, and Google's modern deployment features were ou...
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.