React Native 0.82 marks a historic turning point: it's the first version to run exclusively on the New Architecture, leaving the legacy system behind. This release not only solidifies performance and stability but also introduces experimental features like Hermes V1, React 19.1.1 integration, and DOM Node APIs. Whether you're a seasoned developer or just starting out, understanding these changes is crucial for building modern, efficient mobile apps. Below, we break down the five most impactful elements of this release—each a milestone in React Native's evolution.

1. New Architecture Only: A Bold Leap Forward

React Native 0.82 enforces the New Architecture as the sole operating mode, removing the option to fall back to the legacy system. This decision follows extensive testing and refinement since version 0.76 made it the default. Setting newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS will now be ignored—your app will run on the New Architecture regardless. This streamlines the codebase and reduces technical debt, setting the stage for future improvements like smaller bundle sizes. For developers still on older versions, the recommended path is to first migrate to React Native 0.81 or Expo SDK 54, enable the New Architecture there, and then upgrade to 0.82. This ensures a smooth transition without breaking existing functionality.

2. Experimental Hermes V1: Performance Boost on the Horizon

With version 0.82, React Native offers an experimental opt-in to Hermes V1, the next generation of the JavaScript engine. This upgrade promises faster startup times, reduced memory usage, and improved runtime performance for both iOS and Android. While still in experimental stages, early benchmarks show significant gains in app responsiveness and cold-start speed. Developers can enable it by configuring their build settings—but expect some instability as the engine matures. Think of it as a sneak peek at what's coming: a more powerful, efficient Hermes that will eventually become the default. For those eager to test cutting-edge performance, this is an opportunity to shape the future of React Native through feedback.

3. React 19.1.1 Integration: Enhanced React Features

React 19.1.1 is now bundled with React Native 0.82, unlocking a suite of new features for mobile developers. This update includes improvements to concurrent rendering, automatic batching, and server components—all designed to make apps faster and more responsive. For example, automatic batching reduces unnecessary re-renders, while concurrent rendering prioritizes user interactions for a smoother experience. The upgrade also lays the groundwork for future React features, such as enhanced suspense and streaming capabilities. By staying aligned with the latest React stable release, React Native ensures that mobile apps can leverage the same modern APIs available on the web, bridging the gap between platforms.

4. DOM Node APIs: Bridging Web and Mobile

React Native 0.82 introduces experimental support for DOM Node APIs, a set of interfaces that let developers interact with native views using familiar web-like methods. This includes capabilities like getRootNode, getElementById, and event delegation, which simplify tasks like accessing view hierarchies or handling complex touch interactions. While still experimental, these APIs aim to reduce the learning curve for web developers moving to mobile and enable more consistent cross-platform code. Under the hood, they map to native components, ensuring performance isn't compromised. This feature signals React Native's ongoing effort to unify web and mobile development paradigms, making it easier to build rich, interactive interfaces without writing platform-specific code.

5. Smooth Migration to the New Era

Migrating to 0.82 requires a deliberate, phased approach—but the team has made it as painless as possible. Start by upgrading to React Native 0.81 or Expo SDK 54, which still support both architectures. Enable the New Architecture there, test thoroughly, and fix any issues. Then, once everything works, upgrade to 0.82, which removes the legacy toggle. If a third-party dependency blocks your migration, contact the library maintainers. For bugs in core React Native, use the issue tracker. Looking ahead, the legacy architecture's removal is scheduled for the next version (RFC0929), which will further shrink bundle sizes. Meanwhile, interop layers remain in place to ensure backward compatibility with libraries that haven't fully migrated, giving you breathing room to update at your own pace.

6. Interop Layers: Ensuring Compatibility

To ease the transition, React Native 0.82 retains interop layers that allow legacy architecture code to run alongside the new system. These layers won't be removed soon, so existing third-party libraries that support both architectures will continue to function. The team has verified that libraries offering backward compatibility work without modification. This commitment to stability means you don't have to overhaul your entire dependency tree overnight. However, as future versions remove legacy components, it's wise to migrate libraries to the New Architecture. For now, you can enjoy the benefits of the new system while keeping your current integrations intact. This pragmatic approach balances innovation with developer convenience, reducing risk during the upgrade process.

React Native 0.82 isn't just an update—it's a declaration of intent. By committing entirely to the New Architecture and introducing experimental performance boosters, the platform is accelerating toward a leaner, faster, and more unified future. Whether you're exploring experimental Hermes V1 or leveraging DOM Node APIs, these changes empower you to build better apps with less friction. The migration path is clear, and the community's feedback will shape what comes next. Now is the time to embrace this new era and prepare for the exciting innovations ahead.