React Native 0.82 marks a historic milestone: it’s the first version to run entirely on the New Architecture. No more fallback to legacy code. This release also introduces an experimental Hermes V1, upgrades to React 19.1.1, and adds DOM Node API support. For developers, this means faster performance, smaller bundles, and a cleaner codebase going forward. Below, we answer the most pressing questions about this release and what it means for your projects.
What’s the biggest change in React Native 0.82?
The most significant shift is that React Native 0.82 runs exclusively on the New Architecture. Previous versions, even after making the New Architecture the default in 0.76, still allowed you to fall back to the Legacy Architecture via flags like newArchEnabled=false on Android or RCT_NEW_ARCH_ENABLED=0 on iOS. In 0.82, those flags are completely ignored—your app will use the New Architecture regardless. This is the start of a new era: future releases will strip away legacy code to reduce install size and streamline the codebase. For developers, this means you can finally leverage the full performance, consistency, and modern React features that the New Architecture delivers, without any safety net.
How does the New Architecture–only approach affect me?
If you’ve already migrated to the New Architecture on version 0.81 or Expo SDK 54, upgrading to 0.82 is straightforward. You won’t notice any negative impact—in fact, your app will be faster and more predictable. However, if you’re still on a version that supports legacy architecture (pre‑0.81), you cannot jump directly to 0.82. You must first upgrade to React Native 0.81 or Expo SDK 54, enable the New Architecture there, verify your app works, and then update to 0.82. This stepwise approach ensures a smooth transition. For those blocked by incompatible third-party dependencies, the best course is to contact the library maintainers directly. If you suspect a bug in React Native core is blocking you, report it through the official issue tracker.
What is Experimental Hermes V1 and why does it matter?
Hermes is the JavaScript engine that powers React Native on Android (and optionally on iOS). With 0.82, you can opt in to an experimental new version: Hermes V1. This updated engine brings improved startup time, reduced memory usage, and better debugging capabilities. It’s still experimental, so you need to enable it manually in your configuration. The team recommends testing it on a separate branch or staging environment before rolling out to production. Why should you care? Faster app startup directly translates to a better user experience, and the memory improvements help on lower‑end devices. As Hermes V1 matures, it’s expected to become the default engine in a future release.
What’s new with React 19.1.1 and DOM Node APIs?
React Native 0.82 ships with React 19.1.1, bringing all the latest features from the React core, including concurrent rendering improvements, enhanced Suspense, and better error handling. Additionally, this release introduces DOM Node APIs support. This means you can now use familiar web‑based APIs like document.getElementById() or element.appendChild() directly in your React Native code (within the JavaScript thread). This is a huge productivity boost for web developers transitioning to mobile, as it reduces the mental gap between platforms. Combined with the New Architecture’s Fabric renderer, these APIs are efficient and integrate seamlessly with native components.
How do I migrate my app to React Native 0.82?
The recommended migration path is: Step 1 — Upgrade to React Native 0.81 or Expo SDK 54 (the last versions that allow legacy architecture). Step 2 — Enable the New Architecture in that version and thoroughly test your app. Look for warnings and performance issues that the framework may highlight. Step 3 — Once everything works on the New Architecture, update to React Native 0.82. At this point, the legacy architecture will be locked out. If a third-party dependency is incompatible with the New Architecture, reach out to its maintainers; if you suspect a React Native core bug, file it on GitHub. Remember that interop layers will remain for now, so most libraries that work with both architectures will continue to function.
Will third-party libraries still work? What about interop layers?
Yes, most third-party libraries that offered backward compatibility with both architectures will keep working in React Native 0.82. The React Native team has verified that the interop layers—bridging code that lets legacy library code run on the New Architecture—are staying in the codebase for the foreseeable future. All classes and functions required by those interop layers won’t be removed anytime soon. This gives library maintainers time to fully migrate to the New Architecture. However, if a library never supported the New Architecture, it may break. Always check the library’s documentation and update to versions that explicitly support the New Architecture. The team will share more details later about eventual removal of interop layers.
Are legacy architecture classes being removed in this version?
No, React Native 0.82 does not remove any legacy architecture APIs from the core. To minimize breaking changes and give the ecosystem time to adapt, the team has decided to keep all existing legacy classes and functions intact. However, they have announced that removal of the legacy architecture will begin in the next version. Starting from React Native 0.83, you can expect a significant reduction in bundle size as unnecessary legacy code is stripped out. This aligns with the long‑term goal of a lean, modern React Native. Developers should plan to have their apps fully migrated to the New Architecture by then to avoid disruptions. For details, see RFC0929: Removal of the Legacy Architecture of React Native.