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.

& Łukasz Chludziński

In today’s React Native development landscape, we are no longer building for just mobile. We have the capability to develop for web, automotive, VR and TV. While each platform presents unique challenges developing for the fragmented landscape of TV experiences, in particular, requires balancing consistent app performance across platforms & devices while optimizing for each one’s specific requirements.

So, by sharing our lessons learnt from how to build performant apps for TV, we are essentially sharing React Native performance optimization techniques and best practices for creating scalable, accessible, high-performing apps across multiple operating systems, platforms, and devices.

In this talk, we will explore the intricacies of TV development and how it can help you approach building for a range of different form factors & devices. We will then explore how to structure a scalable codebase and look into strategies for efficient code sharing & feature development. Additionally, we will cover React Native performance optimization techniques as well as debunk how the new React Native architecture impacts performance.

Writing one component is easy. Conditionally rendering two different ones is still not hard. But what if you face an "n" number of permutations. "n" number of different UI elements and scattered business logic? Switch statements all over the place. Might not sound scary when we write the code. What about your future self? Cognitive load fires off the roof. Maintaining your code? Onboarding new devs? Good luck. Sounds all too familiar? Let's see a possible solution how to tame complexity. How to tackle a large number (possibly infinite) of branches in a frontend codebase without losing our sanity.

In this talk, I'll uncover some tricks and hacks in React that I learned while maintaining a micro-library (2KB Router). We'll discuss performance and size optimizations, as well as the importance of keeping object references stable when passing them down as props to React components.

I'd like to cover the non-standard use of the useState hook, cloneElement API for component composition, the useSyncExternalStore hook introduced in React 18, and its caveats; as well as lesser-known non-standard hooks such as useEvent and more. To demonstrate these tricks, we'll built a fake multiplayer client component.