45 articles on Modularization for Android performance
Showing 20 of 45 articles (Page 1 of 3)
Luca from Mercari's Logistics team hit a wall: multiple ViewModels on one screen needed to share data, but Hilt's built-in scopes forced them into Singleton hell with manual cleanup. So they built their own sco...
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.
Erdem Topak from Flink reveals how their Android team scaled from 30 to 437 modules—then discovered 400 unused dependencies silently killing their build times. Here's how they built a custom solution when exist...
Aditya Singh from slice engineering solved a problem that haunts every Android team at scale: navigation crashes from circular dependencies. His team hit zero navigation crashes in production with a runtime gra...
Oleksii Chyrkov from Lyft just closed the book on a 7-year migration journey. The final push to eliminate Java from their entire Android codebase revealed some brutal truths about automated tooling.
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?
Callstack reveals how to add React Native to existing native apps without a full rewrite. This brownfield approach is changing how engineering teams think about cross-platform development.
Reddit's mobile team just dropped their brutally honest take on iOS vs Android development in 2023. Spoiler: neither platform makes it easy.
Gojek's driver app modularization cut CI build times by 33% and unlocked team-level productivity metrics. Here's what they learned from breaking up their monolith.
Sean Coyle from ASOS reveals how they're dismantling their Android monolith using a pattern that slashes recompile times. The secret? Splitting every feature into API and implementation modules.
The article link appears to be broken or unavailable. This is a 404 error page from Medium, not the actual Gojek engineering article about modularizing their Android driver app.
Gojek's Android driver app was drowning: 30-minute CI builds, 10-minute local builds, and a team that had outgrown its monolithic codebase. Something had to give.
Instagram's app was getting bloated. More engineers, more features, slower cold starts, and ballooning app size threatened the lean experience users loved.
Rodrigo Pintos from Mercado Libre reveals how they're tackling a massive problem: keeping 120 million active users happy while their app keeps growing. Their solution? Put the app on a diet.
Rodrigo Pintos from Mercado Libre reveals how they tackled a critical problem: keeping 120M active users from uninstalling their app due to storage constraints. Their solution? Putting their Android app on a di...
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...
Strava's Android team hit a wall trying to modularize their codebase the traditional way. So they flipped their entire architecture upside down.
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...
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.