Introduction

The React Native team is proud to announce the release of version 0.82, marking a significant turning point for the framework. This release is the first to run entirely on the New Architecture, removing the dual-architecture reliance that has defined previous versions. With this milestone, React Native enters a new era of performance, stability, and streamlined development.

Key Highlights of React Native 0.82

Version 0.82 introduces several major updates:

• New Architecture Only – The New Architecture is now the sole engine, with legacy code slated for removal in future releases.
• Experimental Hermes V1 – An opt-in upgrade to a newer version of the Hermes JavaScript engine.
• React 19.1.1 – Updated React core enabling the latest features.
• DOM Node APIs – Support for direct DOM node interactions within React Native.

New Architecture Only

Since React Native 0.76 made the New Architecture the default, the team has been rigorously testing and refining it. With 0.82, the New Architecture becomes the only architecture—any attempts to revert to the Legacy Architecture via configuration flags like newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS will be ignored. This ensures all apps run on the modern, optimized engine.

How to Migrate to the New Architecture

If your project still uses the Legacy Architecture, follow these steps:

1. First, migrate to React Native 0.81 or Expo SDK 54—these are the last versions supporting both architectures and include helpful warnings and performance improvements for the transition.
2. Enable the New Architecture in version 0.81 and thoroughly test your application to confirm everything works.
3. Once verified, update to React Native 0.82. The Legacy Architecture will be automatically disabled, ensuring your app runs exclusively on the New Architecture.

Interop Layers and Third-Party Library Compatibility

To ease the transition, the interop layers that bridge old and new code will remain in the codebase for the foreseeable future. All classes and functions required by these layers will not be removed soon. The team has also verified that third-party libraries offering backward compatibility with both architectures continue to work seamlessly under 0.82.

Removal of Legacy Architecture Classes

While no Legacy Architecture APIs are removed in this version (to minimize breaking changes), future releases will begin stripping out legacy code to reduce app bundle size and simplify the codebase. For details, refer to RFC0929: Removal of the Legacy Architecture.

Experimental Hermes V1

React Native 0.82 includes an experimental opt-in for Hermes V1, a significantly updated version of the Hermes JavaScript engine. This upgrade promises better performance and memory management. To enable it, developers can set the appropriate flag in their configuration. Note that this feature is still experimental and may not be suitable for production applications without thorough testing.

React 19.1.1

The framework now ships with React 19.1.1, bringing the latest features from the React ecosystem. This includes improved state management, concurrent rendering enhancements, and updated hooks. Developers can leverage these improvements to build more responsive and maintainable mobile apps.

DOM Node APIs

Version 0.82 introduces support for DOM Node APIs within React Native. This allows developers to directly manipulate native views using familiar web-style operations, enabling more fine-grained control over the UI. This addition bridges the gap between web and mobile development, making it easier to port web components or create complex custom views.

Looking Ahead

With React Native 0.82, the framework takes a decisive step toward a cleaner, more modern codebase. The removal of the Legacy Architecture, combined with experimental upgrades like Hermes V1 and updated React core, sets the stage for faster iterations and smaller app sizes. Developers are encouraged to plan their migration now and explore the new capabilities. The team will continue to share updates on the deprecation timeline for interop layers and legacy code removal.

For further information, visit the official React Native blog.