React Native 0.82: Key Questions Answered
React Native 0.82 marks a significant milestone as the first version to run entirely on the New Architecture. This update also brings experimental Hermes V1, React 19.1.1, and DOM Node APIs. Here are the key questions answered to help you understand what this means for your development workflow.
Why is React Native 0.82 Considered a Milestone Release?
React Native 0.82 is a landmark version because it is the first release that runs completely on the New Architecture. Previously, developers could toggle between the legacy and new architectures, but now the legacy system is no longer available. This shift paves the way for a leaner, faster React Native. With the removal of legacy code slated for future releases (starting from the next version), the framework will become smaller and more efficient. Additionally, 0.82 introduces experimental Hermes V1 (an upgraded JavaScript engine), updates React to 19.1.1, and adds support for DOM Node APIs. These changes collectively signal the beginning of a new era for React Native, promising better performance, improved developer experience, and a more modern codebase.
What Does "New Architecture Only" Mean for Developers?
In previous versions, the New Architecture was optional — you could set newArchEnabled=false on Android or use RCT_NEW_ARCH_ENABLED=0 on iOS to keep using the legacy architecture. With React Native 0.82, those flags are ignored; your app will always run on the New Architecture. This means developers who haven't migrated must do so now. The legacy architecture is still present in the codebase for backward compatibility of third-party libraries (via interop layers), but it can no longer be selected. The good news is that the React Native team has tested and refined the New Architecture over several releases, so it is stable and production-ready. For new projects, there is no decision to make — you automatically leverage the improved performance, Fabric renderer, and TurboModules.
How Should I Migrate My Project to React Native 0.82?
If you haven't moved to the New Architecture yet, follow these step-by-step recommendations:
- Update to React Native 0.81 or Expo SDK 54 – These are the last versions that allow you to use the legacy architecture. They include helpful warnings and performance improvements to ease the migration.
- Enable the New Architecture in 0.81 – Test your app thoroughly while still being able to fall back to legacy if needed. Verify that all features work correctly.
- Upgrade to React Native 0.82 – Once you are confident in the New Architecture on 0.81, update to 0.82. At this point, the legacy architecture is locked out.
If a third-party library is incompatible, contact the library maintainers directly. If you encounter a core bug, report it on the React Native issue tracker. The interop layers will remain in place for now, so most libraries that worked with both architectures should continue to function.
What is Experimental Hermes V1 and Why Should I Care?
Hermes is the JavaScript engine that powers React Native apps, and Hermes V1 is an experimental upgrade offered in 0.82. It promises improvements in startup time, memory usage, and overall execution performance. While it is opt-in for now, developers can enable it to test their apps and provide feedback. The experimental label means the APIs and behavior might change in future releases, but it's a clear step toward a more optimized runtime. By adopting Hermes V1 early, you can benefit from faster app launches and smoother interactions, especially on lower-end devices. Keep in mind that some features may not be fully stabilized, so thorough testing is recommended before production use.
What Are the React 19.1.1 and DOM Node APIs Updates?
React Native 0.82 ships with React 19.1.1, a recent version of the core library. This brings new React features like improved concurrent rendering, better support for hooks, and performance enhancements. Additionally, the release includes support for DOM Node APIs, which let you work more directly with native DOM-like nodes in your React Native components. This is particularly useful for advanced interactions with the UI tree and for integrating with web-based libraries that expect DOM semantics. Together, these updates make React Native more aligned with the broader React ecosystem, making it easier to reuse knowledge and code between web and mobile projects.
Will My Existing Third-Party Libraries Still Work?
Yes, for the most part. The React Native team has verified that third-party (3P) libraries that offer backward compatibility with both architectures will continue to work on 0.82. The interop layers — bridging code that allows legacy architecture APIs to function on the New Architecture — will be kept in the codebase for the foreseeable future. Classes and functions that these layers depend on won't be removed anytime soon. However, if you rely on a library that hasn't been updated for the New Architecture, you may need to contact its maintainers. The team will share further details later about when interop layers might be phased out, but for now you can upgrade with confidence that most popular libraries remain compatible.
What is the Plan for Removing Legacy Architecture Code?
In React Native 0.82, no legacy architecture APIs have been removed from the core — this is to minimize breaking changes. However, the team has announced that removal will begin with the next version (presumably 0.83). The reason is purely size; the legacy code takes up significant space in the bundle. By eliminating it, React Native will become smaller and faster to load. The plan is documented in RFC0929. Developers are encouraged to ensure their apps and dependencies are fully migrated to the New Architecture now, so that future upgrades are smooth and you can immediately benefit from the leaner framework.