56 articles on Build Time for Android performance
Showing 20 of 56 articles (Page 1 of 3)
Márton Braun from JetBrains drops a critical update: Android Gradle Plugin 9.0 just landed with breaking changes that will affect every Kotlin Android project. Time to update your build configs.
Your modular Android app is building like a monolith. One shared :core module is killing your build times, even when you change a single private implementation detail.
Egor Andreevich just shipped a DI framework migration across 1,500 modules serving tens of millions of users. The build speed improvements? Nearly 60% faster incremental builds.
Pinterest's Android CI builds were bleeding 9 minutes per run because one slow test shard held everything hostage. Their fix? Stop counting tests and start counting seconds.
Chamod Lakmal from PickMe reveals how switching annotation processors can cut Android build times in half. If you're still using KAPT, you're leaving serious performance gains on the table.
Ever spent hours debugging why your React Native Android app won't connect to Metro during development? You're not alone.
Reddit's mobile team had zero professional CI experience. Then they cut build times in half and transformed developer happiness.
Ankit Sharma from slice reveals how his team reclaimed 167 hours of developer time annually by tackling Android build performance head-on. Their systematic approach turned a productivity blocker into a competit...
Maxwell Elliott and Connor Wybranowski from Tinder turned what seemed like a 12-year project into a 6-month sprint. Their secret? Letting the compiler do the heavy lifting instead of manually untangling 150,000...
Piyal Madushanka from PickMe Engineering tackles a problem every scaling mobile team faces: how do you manage multiple regional apps without drowning in build configuration chaos?
Owen Voorhees from Apple just dropped a bombshell: the build engine that powers millions of App Store apps is now open source. This changes everything for Swift developers working across platforms.
Enes İğneci from Teknasyon Engineering breaks down why your Android app might be bloated, slow, and vulnerable. The fix? Two powerful code optimization tools most developers underutilize.
Duolingo's engineers were stuck waiting 50 minutes for every CI build. That's hundreds of hours wasted every week across the team.
Matthew McCullough just dropped a bombshell: Android is ditching its annual release cycle. If you're building for Android, your entire 2025 planning timeline just changed.
alexxozo from Glovo's engineering team discovered that a single line of code change slashed their build time by 30%. The culprit? Java's type inference struggling with large Map definitions.
Yaroslav T from Revolut reveals how managing translations for 6 apps across 330 modules and 33 languages evolved from a simple library to a custom Gradle plugin. The journey took 7 years and countless iteration...
Rolgalan from Glovo's Mobile Platform team reveals how they slashed Android build times through hardware and JVM tuning. Most teams are leaving massive performance gains on the table by ignoring these fundament...
Rolgalan from Glovo cut Android build times by 75%—from 1 hour down to 15 minutes. Here's how they did it, and why most teams are leaving massive performance gains on the table.
Cash App's monolith CI builds were taking 30 minutes at p50. Developers were stuck waiting through multiple build cycles just to get a green merge.
Paul Hundal and Pablo Baxter from Square reveal how they slashed CI analysis time by 80% on a monorepo with 5,000+ modules. Their secret? Getting creative with Gradle's internals.