How we transformed a React monolith into multiple apps inside one codebase.

You always start small: one product, one team, one stakeholder. But once you succeed and need to scale, your original frontend architecture might not be ready for what comes next. As our Sales Process Orchestration Platform expanded to support multiple products and sales channels, our original monolithic application became a bottleneck.
In this talk, I'll share how we transitioned to a domain‑driven, multi‑app architecture while deliberately keeping a single React codebase. You'll see how we applied Domain‑Driven Design concepts on the frontend, structured clear boundaries between sales channels, and used Nx to orchestrate builds, enforce architecture rules, and keep teams moving independently without losing shared foundations.

"Write once, run everywhere" is a promising goal in software development, but one that often breaks down under real-world problems. At Zattoo, building streaming applications across Android, Apple, and Web meant years of separate native stacks that were not aligned, and therefore did not scale. This talk explains how moving to a multiplatform architecture, enabled by Vega as a fourth (React Native first platform), brought us very close to achieving that goal.

React Native has changed a bunch, and if you haven't looked at it lately you're in for some fun. We'll walk through building a real app with (my beloved 😍) Expo. Talk about project setup to app store submission with detours into AI-assisted development and ofc, talk about the casual masochism that is mobile dev.