Discover 78 articles on Modularization in mobile performance
Showing 20 of 78 articles (Page 3 of 4)
Guillermo Mazzola from Glovo cracked a problem that's been frustrating Android library publishers since AGP 7.0: how to ship variant-aware libraries without breaking source code navigation in your IDE.
Huan Nguyen from Afterpay reveals how they architected their Android rewrite to support hundreds of future developers. The secret? A three-tiered modular structure that makes parallel development actually work.
Grab built their entire GrabPay merchant app in React Native, then used those learnings to rebuild core payment features in their main passenger app. The result? Half the maintenance resources with identical pe...
Uber rewrote their entire driver app serving 3 million drivers. How do you ship that without breaking your business?
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.
Alexander Kulabukhov from Bumble Tech reveals the hidden costs of iOS modularization that nobody warns you about. Spoiler: visualizing 50+ module dependencies looks like a tangled mess, and your CI will cry for...
Grab went from one monolithic mobile app to over 1,000 modules. Here's what they learned about scaling a superapp.
Alberto De Bortoli from Just Eat Takeaway reveals how they slashed their iOS CI complexity by consolidating dozens of module repos into one. The result? One PR instead of multiple, faster iteration, and smarter...
Tom Doron from the Swift Core Team just made package discovery way less painful. Swift 5.5 introduces Package Collections, turning endless search results into curated, trustworthy lists.
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?
Bumble's iOS team hit a wall: dozens of engineers, hundreds of modules, and Xcode was buckling under the pressure. Sound familiar?
Tokopedia's iOS team faced a critical problem: their monolithic app took so long to build that it threatened their weekly release schedule.
Bumble's iOS team migrated their entire codebase to Tuist in Q2 2023, choosing it over SPM and Bazel. Here's what happened after the dust settled.
Dmitri Fuerle from OkCupid reveals how their team cut clean build times to under a minute by modularizing their iOS codebase. The secret? Swift Package Manager in a monorepo setup.
Anisha Inas Izdihar and Yusuf Cahyo Nugroho from Traveloka tried implementing Dynamic Feature Modules in 2019 when documentation was scarce and critical tools were broken. Their workarounds got creative: they l...
Alexander Kulabukhov from Bumble reveals how his team scaled from a monolithic iOS app to 110+ modules across Badoo and Bumble. The journey wasn't just about splitting code—it was about building a sustainable p...
Jean-Baptiste Vincey from Deezer reveals how their team manages private Android libraries across multiple apps—without the chaos. Their approach handles 3 major libraries with bi-weekly releases and keeps depen...
David Phan from DoorDash reveals how they rebuilt two distinctly branded iOS apps from a single codebase after acquiring Caviar. The result? 90% shared code with completely different user experiences.