Discover 59 articles on Scalability in mobile performance
Showing 20 of 59 articles (Page 2 of 3)
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.
Meetup sends 8-10 million notifications daily. Their queue kept backing up, sending messages late or not at all.
Strava's Android team hit a wall trying to modularize their codebase the traditional way. So they flipped their entire architecture upside down.
Gojek runs 15,000+ VMs across 250+ GCP projects serving millions of customers. How do they manage infrastructure at this scale without chaos?
Tokopedia cut their Android app download size by 10% using Dynamic Features. But the implementation wasn't as simple as Google's docs suggested.
Uber rewrote their Android rider app in 2016 and made an architectural choice that most Android teams avoid: deeply nested dependency injection scopes.
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%.
Slack's mobile codebase was slowing teams down. Their solution? Break the monolith into hundreds of independent modules.
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.
Larry McKenzie and Corey Sprague from eBay built a full-featured mobile app in under a year with a tiny team. Their secret? Ditching the traditional native approach entirely.
Callstack explores why staying current with React Native versions isn't just about new features. It's the difference between a performant app and technical debt that compounds with every release.
Swift is taking on distributed systems with the same elegance it brought to concurrency. The Swift team just open-sourced a complete cluster library for building distributed actor systems.
Walmart's engineering team learned the hard way: breaking up a monolith without fixing team structure just creates a distributed mess.
Bartosz Klonowski from Callstack breaks down why React Native Windows isn't just about cross-platform code. It's about predictable timelines and lower maintenance costs that CFOs actually care about.
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.
Tokopedia's iOS team just wrapped up their modularization tutorial series, and the final piece is a game-changer: micro apps that let you build only what you need.
Grab went from one monolithic mobile app to over 1,000 modules. Here's what they learned about scaling a superapp.
Microsoft's mobile teams were drowning in duplicate code. Every app rebuilt the same file picker, calendar, and sharing experiences from scratch.
Tokopedia's iOS team tackled a common scaling problem: how do you break apart a monolithic app without creating circular dependency chaos?
Tokopedia's iOS team faced a critical problem: their monolithic app took so long to build that it threatened their weekly release schedule.