React Native 0.82: The Dawn of a New Architecture-Only Era

Introduction

React Native 0.82 marks a pivotal moment for mobile development. For the first time, this release runs entirely on the New Architecture, eliminating dependency on the legacy system. This milestone not only simplifies the codebase but also sets the stage for future enhancements. In addition to architecture changes, version 0.82 introduces experimental Hermes V1 support, updates React to version 19.1.1, and includes DOM Node APIs. Let's dive into these features and what they mean for your projects.

New Architecture Only

Since React Native 0.76 made the New Architecture the default, the team has rigorously tested and refined it. With 0.82, the New Architecture becomes the sole option. Attempts to disable it (e.g., newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS) are now ignored—your app will always use the New Architecture. This shift ensures consistency and allows the team to focus on optimizing performance and reducing code complexity.

Benefits of the New Architecture

• Faster startup times due to leaner initialization
• Better type safety with JSI (JavaScript Interface)
• Improved interoperability with native modules
• Enhanced debugging and error reporting

How to Migrate Safely

If you haven’t yet migrated to the New Architecture, follow these steps to ensure a smooth transition:

1. Upgrade to React Native 0.81 or Expo SDK 54 – These are the last versions that support the Legacy Architecture. They include helpful warnings and performance improvements designed to ease migration.
2. Enable the New Architecture in 0.81 and thoroughly test your application. Verify that all features work as expected.
3. Update to React Native 0.82 once you’re confident in the New Architecture. This version permanently disables the legacy option.

If a third-party dependency is blocking your migration, reach out to its maintainers. For core React Native bugs, use the issue tracker to report them.

Interop Layers and Third-Party Library Compatibility

To ease the transition, React Native 0.82 retains interop layers—bridging code that allows legacy components to work with the New Architecture. These layers will remain for the foreseeable future, and no immediate removal of required classes or functions is planned. We’ll provide advance notice before deprecating them.

Moreover, libraries that currently support both architectures will continue to function in 0.82. The team has verified that the shift to a single architecture does not break backward-compatible third-party libraries.

Removal of Legacy Architecture Classes

In this version, no legacy APIs have been removed from the core—ensuring backward compatibility and minimizing breaking changes. However, removing the Legacy Architecture code is a priority for reducing bundle size. Starting from the next React Native version, the cleanup will begin, in line with RFC0929. Stay tuned for details on which APIs will be phased out.

Other Key Enhancements

Experimental Hermes V1

React Native 0.82 introduces an opt-in for Hermes V1, the next generation of the Hermes JavaScript engine. While still experimental, it promises improved startup performance and smaller bundle sizes. Developers can test it by configuring their build settings—look for the hermesVersion option.

React 19.1.1

This release includes React version 19.1.1, which brings new hooks, better concurrent rendering, and optimized state management. Upgrading ensures your app benefits from the latest React capabilities, such as useOptimistic and improved Suspense behavior.

DOM Node APIs

Support for DOM Node APIs bridges the gap between React Native and web development. Now you can use familiar methods like getBoundingClientRect and querySelector directly in your React Native code, simplifying cross-platform work.

Looking Ahead

React Native 0.82 is more than an incremental update—it’s a declaration of intent. By fully committing to the New Architecture, the platform is laying a foundation for smaller, faster, and more maintainable apps. The experimental Hermes V1 and DOM APIs hint at an exciting future. If you haven’t yet migrated, now is the perfect time to start planning your upgrade path.