Back in the 2000s, browsers shipped once a year: with cake, fireworks, and a press tour. In the 2010s, releases jumped to 6–8 a year. In the 2020s we’re already looking at a dozen a year, and by the end of 2026 most browsers will start shipping every two weeks. Even if you’re a 10x god with a herd of LLM agents at your back, their models were trained six months ago, and they’re often simply out of the loop, and they'll lie to your face with a smile. What's already possible, what still isn't, and how to actually stay on top of everything happening on the web platform.

In State of Brownfield in React Native, we’ll look at how engineering teams can introduce React Native and JS into mature, native-only applications. The session walks through practical strategies for phased adoption, cutting-edge tooling, and effective architectural choices. We’ll dig into the real challenges that come with hybrid integration and wrap up with advanced areas like brownfield state and data exchange.

The talk examines how teams can bring React Native and JavaScript into an existing native-only tech stack. We’ll look at practical approaches for gradual adoption—ensuring that iOS and Android apps can continue to receive features and fixes while part of the development workload shifts toward React Native. The session highlights state-of-the-art tooling, integration strategies, and architectural patterns that make brownfield adoption more seamless, while also addressing the real-world challenges that commonly arise in hybrid environments. We’ll conclude by exploring advanced topics such as preloading, passing initial props from native to JS, and efficient bi-directional communication between native code and JavaScript

Agentic engineering speeds up development, but fast-paced changes make edge cases—like onboarding flows and error handling—easy to miss.
Using Metro’s custom resolver, we can now launch directly into specific test environments, like targeted edge cases or simulated errors, without cluttering our production code with feature flags.

When TypeScript gets too slow, native modules can help. We’ll look at the available options and see why Nitro Modules are especially worth trying.