Discover 78 articles on Modularization in mobile performance
Showing 18 of 78 articles (Page 4 of 4)
Keith Smiley from Lyft just announced something that could change how we all build mobile apps. Instead of every company rebuilding the same infrastructure in silos, major tech players are finally collaborating...
Rob Pridham from BBC Sport reveals how his team tackled a massive Android refactor—migrating from multiple activities to a single-activity architecture while keeping the app running in production.
Netflix just went all-in on Kotlin Multiplatform for their production studio apps. Here's why they're betting on shared code over platform-specific rewrites.
Uber threw away years of code and rebuilt their rider app from scratch. Here's why that radical decision paid off.
Snapchat shipped two complete Android apps in a single APK to A/B test their rewrite. The engineering challenge? Android wasn't designed to support this at all.
Spotify lifted the 10,000 Liked Songs limit. But that simple feature request triggered a year-long architecture overhaul affecting 100,000 lines of code.
Shopify scaled to multiple mobile apps without slowing down. Their secret? Stop treating apps like special snowflakes.
Alifa Nurani Putri and Yusuf Cahyo Nugroho from Traveloka reveal how their single Dagger component ballooned to 17,705 lines of code across 25+ products. Their refactoring journey cut initialization time and bu...
Callstack explores how to add React Native to existing Android apps without a full rewrite. This brownfield approach lets teams ship cross-platform features while keeping their native codebase intact.
Robinhood's Android team cracked a tough modularization puzzle: how do you navigate between completely decoupled feature modules without creating dependencies?
Callstack tackles one of React Native's toughest scaling challenges: building component libraries that actually work across teams. Most companies get this wrong and pay for it later.
Robinhood's Android app hit a wall: 100k+ dex count, skyrocketing build times, and features breaking each other. Sound familiar?
Junius Ang from Traveloka reveals how their 'District System' lets a 5-person team manage multiple React Native apps across brownfield and greenfield projects. The secret? It's not a framework—it's a reusabilit...
Todd Santaniello from Strava reveals what happened when their entire Android team stopped shipping features for a week. The goal? Break apart a 6.5-year-old monolithic codebase that was crushing build times and...
Guillermo Orellana from Bumble's tech team walks through the real-world pain of integrating React Native into an existing Android app. Spoiler: the official docs won't save you.
Uber scaled from a dozen iOS engineers to hundreds in just a few years. Their tooling nearly collapsed under the weight.
Uber completely rewrote their rider app from scratch. Here's why they threw away years of code and started over.
Felipe Cypriano from Thumbtack reveals how migrating iOS apps to frameworks nearly derailed their Swift adoption—until they discovered a clever workaround for binary dependencies.