56 articles on Build Time for Android performance
Showing 20 of 56 articles (Page 2 of 3)
Premise's mobile team caught a sneaky 3x build time regression that only showed up in CI. Here's how they hunted it down using Gradle Enterprise.
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.
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...
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...
Cash App's team turned a frustrating 20-second hot reload into a blazing 2.7 seconds. Here's how they systematically hunted down every millisecond.
Doni Winata from Traveloka's Android Infra team reveals how his team automated build benchmarking to catch performance regressions before they hit production. For projects with 300+ modules and 15-20 minute bui...
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.
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.
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.
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.
Ryan Harter from Dropbox just open-sourced a Gradle plugin that cuts Android Studio sync time by 87%. If you're tired of waiting on builds in large Android projects, this is for you.
Reddit's mobile team ships features 30% faster after overhauling their developer productivity infrastructure. Here's how they did it.
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.
Doist went from scary 2-hour manual Android releases to shipping every single day. Here's the engineering playbook that made it possible.
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...
Pinterest's Engineering Productivity team slashed CI build times by over 50% in one week. Here's the architecture that made it possible.
Yury from Bumble Tech tackles a painful Gradle problem: buildSrc invalidates your entire build cache with every change. Here's how composite builds solve it without sacrificing IDE support.
Snapchat shipped two complete Android apps in a single APK to A/B test their rewrite. The engineering challenge? Android wasn't designed to support this at all.
LinkedIn's Android test suite hit tens of thousands of tests, pushing execution times into the danger zone. Developer productivity was tanking.
Spotify cut iOS pre-merge CI times by 75% with one infrastructure change. Here's how they validated and scaled their approach.