> Markdown version of [/videos/100313-multiple-apps-millions-of-users-scaling-react-native-in-production?t=1626](https://www.wearedevelopers.com/videos/100313-multiple-apps-millions-of-users-scaling-react-native-in-production?t=1626). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Multiple Apps, Millions of Users: Scaling React Native in Production Overloaded UI components tanked their performance. Discover how extracting business logic into view models scaled this React Native monorepo to millions of users. - **Speakers:** [Milica Aleksic](https://www.wearedevelopers.com/@milica-aleksic) - **Event:** World Congress 2026 Europe - **Published:** July 10, 2026 - **Duration:** 31:45 - **URL:** https://www.wearedevelopers.com/videos/100313-multiple-apps-millions-of-users-scaling-react-native-in-production ## Summary The evolution of a single React Native application into a multi-product portfolio serving millions of users brings profound architectural challenges. Initially, a single news portal was scaled to support a second country by heavily sharing UI components. However, this shared UI gradually morphed into shared product logic. Overloaded components carrying conditional rules for ads, analytics, and platform behaviors ultimately tanked mobile scroll performance and bloated the codebase. When a third application required a separate repository, technical debt peaked. Maintenance tripled, cross-repo bug tracking blurred team ownership, and routine React Native ecosystem upgrades dragged on for six weeks. To survive, the engineering team halted feature development for a critical workshop, pivoting from asking what could be reused to mapping true business capabilities. The core refactor involved aggressively stripping business logic, feature flags, and API context out of the UI components and shifting it into view models. Rather than managing complex nested logic, the UI became lightweight components that simply rendered injected data and fired events. Today, the operation successfully powers five distinct applications using a single unified repository, one continuous integration pipeline, and a modular architecture governed by a strict design system. The transformation underscores a crucial reality in mobile scaling: architecture should optimize for the next five years, not the next sprint. As the team experienced firsthand, "good architecture isn't something you design from the ground up, it's something you discover," and it must continuously evolve faster than the products it supports. **Keywords:** react native scaling, white-label applications, shared ui components, business logic extraction, mobile view model architecture, cross-platform development, monorepo transition, react native ecosystem upgrades, mobile application performance, design system tokens, technical debt management, news portal application scaling, mobile ci/cd pipelines ## Chapters 1. **The journey from one to many mobile applications** (00:08) — The need to scale transformed a single mobile application into five independent products over five years. 1. **Choosing React Native for mobile application growth** (03:02) — Team experience and cross-platform capabilities made React Native the ideal choice for rapid initial development. 1. **Building the initial news portal application** (05:00) — Developing the first news application required establishing robust platform features like notifications and offline caching. 1. **Approaching the scaling challenge of a second product** (07:06) — Tight deadlines for a second product forced the team to evaluate monorepo setups against code duplication. 1. **The performance cost of overloaded interface components** (12:40) — Forcing shared user interface components to manage divergent business logic caused severe scrolling and rendering bottlenecks. 1. **Maintenance overhead across multiple divergent code repositories** (16:04) — Managing three disconnected repositories turned framework upgrades and persistent bug fixes into a severe maintenance bottleneck. 1. **Extracting business logic to rescue application architecture** (20:34) — The team halted feature development to redesign interface components to pull data exclusively from external view models. 1. **Implementing layered shared infrastructure for multiple products** (24:45) — A layered architecture approach successfully consolidated five separate portals into a single shared deployment pipeline. 1. **Evaluating tooling alternatives and optimal repository setups** (27:06) — Tooling alternatives like Expo and architectural benefits of monorepos offer different trade-offs for scaling applications. ## Related Moments - [Defining native applications and the history of React](https://www.wearedevelopers.com/videos/277-hands-on-react-native-from-zero-to-hero) (from "Hands-on React Native: From Zero to Hero") - [Navigating continuous delivery for React Native mobile applications](https://www.wearedevelopers.com/videos/556-the-perfect-ci-cd-react-native-pipeline-with-fastlane) (from "The perfect CI/CD React Native pipeline with Fastlane") - [Origins and architectural capabilities of the React Native framework](https://www.wearedevelopers.com/videos/556-the-perfect-ci-cd-react-native-pipeline-with-fastlane) (from "The perfect CI/CD React Native pipeline with Fastlane") - [Overcoming challenges of scaling legacy monolithic frontend applications](https://www.wearedevelopers.com/videos/236-microfrontends-at-scale) (from "Microfrontends at Scale") - [Transitioning developers from React web to React Native mobile](https://www.wearedevelopers.com/videos/448-challenges-of-building-react-and-react-native-apps) (from "Challenges of building React and React Native apps") - [Evolving frontend application architectures from simple to enterprise scale](https://www.wearedevelopers.com/videos/1682-client-side-state-management-reimagined-think-outside-the-box) (from "Client-Side State Management Reimagined – Think Outside the Box") ## Related Articles - [Native Web Apps: Are We There Yet?](https://www.wearedevelopers.com/magazine/83-native-web-apps-are-we-there-yet) - [16 Best Free React UI Libraries in 2025](https://www.wearedevelopers.com/magazine/148-16-best-free-react-ui-libraries-in-2025) - [Dev Digest 103 - Superb Owl Trafficking](https://www.wearedevelopers.com/magazine/388-dev-digest-103-superb-owl-trafficking) - [A Guide to Choosing the Right Tools for App Developers](https://www.wearedevelopers.com/magazine/391-a-guide-to-choosing-the-right-tools-for-app-developers) ## Related Jobs - [Senior React Native Developer](https://www.wearedevelopers.com/jobs/ext/1518176-senior-react-native-developer) at **Almedia** - [Junior Frontend Engineer](https://www.wearedevelopers.com/jobs/ext/1532351-junior-frontend-engineer) at **Almedia** - [Founding Mobile Engineer (iOS)](https://www.wearedevelopers.com/jobs/ext/1648532-founding-mobile-engineer-ios) at **Almedia** - [Senior Software Engineer, Client Apps Platform](https://www.wearedevelopers.com/jobs/ext/1773893-senior-software-engineer-client-apps-platform) at **GitHub** - [Senior Software Engineer, React (Investing & Trading)](https://www.wearedevelopers.com/jobs/ext/1937625-senior-software-engineer-react-investing-trading) at **Bitpanda** - [React Engineer for Next.js UI - Hybrid, Impactful FinTech](https://www.wearedevelopers.com/jobs/ext/1444505-react-engineer-for-next-js-ui-hybrid-impactful-fintech) at **Bitpanda**