Android × Scalability
Android Scalability
We track 36 Android Scalability case studies from 27 engineering teams. Gojek, Uber and Glance write about it most. Many posts also cover Modularization and Architecture. The posts run from 2012 to 2025. The newest is from November 2025.
Android Scalability articles 1–30 of 36
The Ultimate Kotlin Multiplatform Watchlist
Ekaterina Petrova curated 10 KotlinConf talks that show how Duolingo, McDonald's, and StoneCo achieved massive scale with Kotlin Multiplatform. Skip the beginner mistakes and learn from teams already shipping t...
Android Engineering Strategy for Global App Launch
Karthi from Mercari's Android team reveals why they ditched cross-platform frameworks for their global marketplace launch. The decision wasn't about native vs. hybrid ideology, it was about leveraging 10M+ down...
Flutter for Enterprises: Everything CTOs and Engineering Leaders Need to Know
Very Good Ventures reveals why global leaders like Disney, Toyota, and BMW are ditching fragmented native development for a single framework. The shift isn't just technical—it's transformational.
Managing Dependency Hell in a 400-Module Android Project
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...
How Uber Standardized Mobile Analytics for Cross-Platform Insights
Uber runs 50+ mobile apps across iOS and Android. How do you get consistent analytics when every team tracks things differently?
Scaling Swiggy's Mobile Ecosystem [1/n]
Tushar Tayal from Swiggy reveals the hidden complexity behind managing 6+ consumer apps (Snacc, Instamart, Toing, Dineout, Crew) in production. Spoiler: it's not just about shipping faster.
Boosting App Performance: Strategies to Optimize Network Requests
Coinbase cut network requests by 64% during traffic spikes without degrading user experience. Here's how they engineered their way to massive scale.
Distributed Job Scheduler: Zero to 20k Concurrent Jobs
Glance built a distributed job scheduler that went from zero to handling 20,000+ concurrent jobs. Here's how they did it with Redis and smart architecture.
Scaling Glance Game Centre to Support 100 Million Daily Active Users
Glance Game Centre serves millions of daily users playing HTML5 games on their lock screens. Their leaderboard system hit a wall with a single-node MongoDB struggling under 1000 QPS.
Modularizing Our Driver App for Android: Benefits & Way Ahead (Part-3)
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.
Slack Behind the Scenes: Overcoming Key Challenges to Craft a Seamless Mobile App
Tracy Stampfli from Slack reveals how her infrastructure team keeps 120+ mobile engineers shipping features without breaking the app. The secret? Treating mobile connectivity like a first-class problem, not an ...
Preventing App Performance Degradation Due to Sudden Ride Demand Spikes
Grab's engineering team faced a brutal problem: rain in Southeast Asia would crash their entire ride-hailing system. When demand spiked locally, users everywhere suffered.
Modularizing Our Driver App for Android: The Need (Part-1)
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.
GoTransit: Unifying Our Mobility Products with Public Transportation
The article link appears to be broken or unavailable. I cannot access the content about GoTransit's mobility integration.
Scaling Mobile Device Management
Uber's Client Platform Engineering team faced a massive challenge: rolling out MDM to 20,000+ employees across hundreds of global offices where standard Apple enrollment wouldn't work everywhere.
Strategies and Tools for Performing Migrations on Platform
Spotify migrated 2,200+ mobile components and moved their entire iOS/Android codebase to Bazel across 100+ squads. Here's how they survived the chaos.
How Meetup Scales Notification Queue Consumers
Meetup sends 8-10 million notifications daily. Their queue kept backing up, sending messages late or not at all.
Android Guild Week 2: More Modules
Strava's Android team hit a wall trying to modularize their codebase the traditional way. So they flipped their entire architecture upside down.
Introducing Skynet: Infrastructure as Code for Gojek
Gojek runs 15,000+ VMs across 250+ GCP projects serving millions of customers. How do they manage infrastructure at this scale without chaos?
The Benefits and Challenges of Android Dynamic Feature in Tokopedia
Tokopedia cut their Android app download size by 10% using Dynamic Features. But the implementation wasn't as simple as Google's docs suggested.
Managing Deep Scope Hierarchies in Large Codebases
Uber rewrote their Android rider app in 2016 and made an architectural choice that most Android teams avoid: deeply nested dependency injection scopes.
Scaling Slack’s Mobile Codebases: Modernization
Slack just wrapped a massive mobile refactor. The results? 68% of iOS and 92% of Android codebases modernized, with CI times slashed by over 60%.
Scaling Slack’s Mobile Codebases: Modularization
Slack's mobile codebase was slowing teams down. Their solution? Break the monolith into hundreds of independent modules.
Building a Thoughtful Scaling Framework for Engineering
Robinhood doubled their engineering team in a year while scaling to handle unpredictable market swings. Here's the framework that made it possible without breaking their systems or culture.
Tech Modernization at scale — Blog Series
Walmart's engineering team learned the hard way: breaking up a monolith without fixing team structure just creates a distributed mess.
Scaling Android Apps with Gradle: Different Source Sets (Part 2)
OLX Engineering scaled their Android app across multiple markets without creating code chaos. Here's how they used Gradle source sets to keep things clean.
App Modularisation at Scale
Grab went from one monolithic mobile app to over 1,000 modules. Here's what they learned about scaling a superapp.
Scaling Mobile Development at Microsoft: Mental Model
Microsoft's mobile teams were drowning in duplicate code. Every app rebuilt the same file picker, calendar, and sharing experiences from scratch.
Leveraging Mobile Infrastructure with Data-Driven Decisions
Spotify's mobile infrastructure team turned build time chaos into predictable performance. Their secret? Making every engineer a data scientist.
Blibli.com Android Evolution
Cesario Putera from Blibli.com shares a brutally honest story: their Android app went through 4 complete rewrites, each time drowning in technical debt. The fourth attempt? They couldn't afford to stop and rebu...