React Native 0.82: Everything You Need to Know About the New Architecture Era

React Native 0.82 marks a pivotal moment in mobile development: it is the first version that runs entirely on the New Architecture. This release eliminates the legacy architecture as an option, paving the way for a leaner, faster, and more modern React Native. Alongside this milestone, version 0.82 introduces experimental support for Hermes V1, upgrades React to 19.1.1, and adds support for DOM Node APIs. Below, we break down the most important changes and what they mean for your projects.

What is the biggest change in React Native 0.82?

The single biggest change is that the New Architecture is now the only architecture. Previously, developers could toggle between the New and Legacy architectures using flags like newArchEnabled on Android or RCT_NEW_ARCH_ENABLED on iOS. Starting with React Native 0.82, those flags are ignored, and your app will always run on the New Architecture. This decision comes after extensive testing and refinement since the New Architecture became the default in version 0.76. The team is confident that the New Architecture delivers improved performance, better memory management, and a more modern foundation for future features. For developers, this means a one-way door: once you upgrade to 0.82, you cannot revert to the Legacy Architecture.

Why did the React Native team decide to make the New Architecture the only option?

The decision to remove the Legacy Architecture was driven by the need to reduce maintenance overhead and streamline the codebase. Maintaining two parallel architectures required significant effort and slowed down innovation. By making the New Architecture mandatory, the team can focus all resources on optimizing and expanding its capabilities. Additionally, the removal of legacy code will eventually lead to a smaller bundle size and faster install times. The team has announced that the actual removal of Legacy Architecture classes will begin in the next version, following the blueprint outlined in RFC0929. This version (0.82) still retains backward compatibility with existing APIs, but it clears the path for a cleaner, more efficient React Native in future releases.

How should developers migrate from the Legacy Architecture to 0.82?

The recommended migration path is a two-step process:

• First, upgrade to React Native 0.81 or Expo SDK 54 — these are the last versions that still allow using the Legacy Architecture. They include specific warnings and performance improvements to help smooth the transition.
• In that version, enable the New Architecture and thoroughly test your app to ensure everything works correctly (including all third-party dependencies).
• Once you are confident in the New Architecture’s stability, you can safely upgrade to React Native 0.82, which locks the New Architecture as the only option.

If an incompatible third-party library blocks your migration, contact the library maintainers directly. If you suspect a bug in React Native core, report it via the official issue tracker. The interop layers that support backward compatibility will remain in place for the foreseeable future, so most libraries that already work with both architectures should continue to function.

What about third-party library compatibility in this version?

The React Native team has verified that third-party libraries offering backward compatibility with both architectures will continue to work in 0.82, even though the Legacy Architecture is no longer selectable. The interop layers — the code that bridges the gap between old and new — will remain in the codebase for the time being. This means that if a library previously supported both architectures, it should still function without changes. However, libraries that rely exclusively on the Legacy Architecture’s internal APIs may require updates. The team recommends reaching out to library maintainers if you encounter issues. Future versions will remove the interop layers, so library authors are encouraged to fully embrace the New Architecture to avoid breakage down the line.

What are the experimental Hermes V1 and React 19.1.1 updates?

React Native 0.82 includes two notable experimental and version updates:

• Experimental Hermes V1 — This is a newer version of the Hermes JavaScript engine, available as an opt-in. While still experimental, it promises potential performance and memory improvements over the current Hermes engine. Developers can enable it and test their apps, but it is not yet recommended for production.
• React 19.1.1 — The underlying React library has been updated to version 19.1.1, which brings the latest features, bug fixes, and performance enhancements from the React ecosystem. This ensures that React Native stays aligned with the web React release.

Additionally, support for DOM Node APIs has been shipped, allowing developers to programmatically interact with native UI elements in a more familiar way. These new capabilities further blur the line between React Native and web development.

Will the Legacy Architecture code be completely removed soon?

In version 0.82, no Legacy Architecture APIs have been removed from the core. The team has deliberately retained backward compatibility to minimize breaking changes and allow developers time to fully migrate. However, the removal process is scheduled to begin with the next version of React Native. RFC0929 details the plan: removing the Legacy Architecture classes will significantly reduce the overall bundle size and simplify the codebase. The interop layers will also be removed eventually, but the team will announce further updates before that happens. For now, developers are encouraged to ensure their apps and dependencies are fully compatible with the New Architecture, as the safety net of the Legacy Architecture will gradually disappear.