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.

WebStorm IDE is researching developer experience flow state. We found that developers feel it is not productive alt-tabbing between IDE/ AI Agents, Figma and browsers trying to spot if everything matches. It’s a manual process that doesn’t scale when we are getting faster with AI. It's too late if these visual bugs hit a PR review, you've already lost the context needed to fix them without taxing your head space.

Is it possible or even desired to pull this validation directly into the development loop?
We'd like to show you our prototype on how we would like to combine the Figma Plugin APIs, WebStorm and Vitest Browser Mode to automate these checks while you code.

In this talk, we’ll explore the performance limits of SVG when rendering scatter charts with thousands of data points, based on our experience at MUI X Charts. You’ll learn how to identify bottlenecks, performance measuring tricks, and the techniques we use to optimize rendering.

In this talk, we'll dive into Client-Side Semantic Caching. I'll show you how to intercept user prompts in the browser, run a tiny open-source AI model locally to understand the "meaning" of the text, and serve previously cached answers instantly. We will look at real code using Transformers.js and IndexedDB to drop your AI latency to 0ms, save API tokens, and build a greener web