React Native 0.82: Your Guide to the New Architecture Era

Welcome to the next chapter of React Native! Version 0.82 marks a pivotal shift: it's the first release to exclusively run on the New Architecture. This means no more toggling between old and new — the future is here. Alongside this change, you'll find experimental support for Hermes V1, an update to React 19.1.1, and new DOM Node APIs. In this Q&A, we answer the most pressing questions about migrating, compatibility, and what comes next.

1. What makes React Native 0.82 a milestone release?

React Native 0.82 is the first version that runs entirely on the New Architecture. This is a major step forward because it means all the performance and flexibility improvements introduced in the New Architecture are now the standard. The Legacy Architecture is no longer available for use in this release — setting newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS will be ignored. The core team believes this is the dawn of a new era, with future versions removing remaining legacy code to slim down bundle size and simplify the codebase. For developers, this translates to a more stable foundation and easier maintenance going forward.

2. How does the New Architecture become the only option?

Since React Native 0.76 made the New Architecture the default, the team has been refining it through testing and feedback. Now in 0.82, it's the sole architecture. Any attempt to revert to the Legacy Architecture through build flags will no longer work. This change ensures that all apps benefit from the New Architecture's improvements, such as synchronous layout, better interop with native modules, and reduced overhead. If you haven't migrated yet, the recommended path is to first move to React Native 0.81 or Expo SDK 54 (the last versions supporting both) and enable the New Architecture there. Once verified, you can safely upgrade to 0.82.

3. What key features ship with React Native 0.82?

Besides the exclusive New Architecture, version 0.82 introduces three major enhancements:

• Experimental Hermes V1 — An opt-in upgrade to a newer version of the Hermes JavaScript engine, promising improved startup times and smaller bundle sizes. It's experimental, so you can try it and provide feedback.
• React 19.1.1 — The React library is updated, bringing the latest features and bug fixes from the React ecosystem.
• DOM Node APIs — Support for DOM-style node manipulation in the React Native environment, making it easier for web developers to feel at home.

These additions together make 0.82 a feature-rich release that pushes the platform forward.

4. How do I migrate to React Native 0.82 safely?

If you're still on the Legacy Architecture, follow this step-by-step plan:

1. Upgrade to 0.81 or Expo SDK 54 — These versions allow you to keep the Legacy Architecture while preparing for the New Architecture. They include warnings and optimizations to help migration.
2. Enable the New Architecture in 0.81 — Test your app thoroughly. Ensure all features work, including third-party libraries.
3. Update to 0.82 — Once everything runs smoothly with the New Architecture on 0.81, you can safely switch to 0.82. Legacy Architecture flags will be ignored, but your app will continue using the New Architecture.

If a third-party library is blocking you, contact its maintainers directly. For core React Native bugs, open an issue on the official tracker.

5. What about compatibility with third-party libraries and interop layers?

The team understands that many projects rely on third-party (3P) libraries. To ease the transition, the interop layers — which allow legacy components to work with the New Architecture — will remain in the codebase for the foreseeable future. No classes or functions needed by these layers will be removed soon. Libraries that already support both architectures will continue to function in 0.82. If you maintain a library, ensure it is compatible with the New Architecture to avoid issues. The team will share specific timelines for interop layer removal in later announcements.

6. Will the Legacy Architecture be completely removed? When?

In React Native 0.82, no Legacy Architecture APIs are removed — backward compatibility is preserved to reduce breaking changes. However, the removal of legacy code is scheduled to begin in the next version. This will significantly reduce the overall bundle size and streamline the React Native core. For details, check the RFC0929: Removal of the Legacy Architecture. Developers should plan to fully migrate to the New Architecture now to avoid disruption. The transition is happening step by step, so acting early ensures a smooth ride.