React Native 0.82 Released with new Architecture and Hermes V1

React Native 0.82 introduces major milestones: it runs exclusively on the New Architecture, offers an experimental opt-in for Hermes V1 (the next-gen JS engine), upgrades to React 19.1.1, and adds DOM-Node APIs for native components.

• The “New Architecture Only” shift means even if legacy flags are set, the app will run using the new engine.
• Hermes V1 shows benchmark improvements: bundle load and TTI (Time To Interactive) improved in real-world apps.
• The React update enables features like useDeferredValue and startTransition reliably in React Native.
• The addition of DOM-like node APIs allows e.g. element.parentNode, getBoundingClientRect() on native views — bridging web and native paradigms.
• Additional changes: web performance APIs (in canary), a new debugOptimized build type for Android, and a set of breaking changes (e.g., uncaught promise rejections now raise console.error, some private API removals).

Key Enhancements and Implications

• New Architecture Only: By removing support for the legacy architecture at runtime, the codebase simplifies and the default path becomes the new design. Apps migrating now will benefit from fewer legacy constraints and can expect future versions to drop legacy scaffolding entirely.
• Hermes V1 (experimental): The updated engine shows better performance characteristics — faster bundle loading and improved TTI. While still experimental, this gives developers a preview of next-level performance in React Native apps.
• React 19.1.1 Upgrade: This ensures the latest React features work as expected in mobile environments — previously some features had edge cases in React Native; now they align more closely with web behavior.
• DOM Node APIs for Native Components: Native components now expose a subset of web-like DOM APIs via refs. This improves interoperability and could make cross-platform tooling and migration from web to mobile more straightforward.
• Performance & Build Enhancements: The debugOptimized variant on Android allows faster dev iteration (approaching release-build performance) while retaining JS debugging. The inclusion of web performance APIs (in canary) opens doors for better telemetry and profiling in mobile apps.
• Breaking Changes & Migration: Some behaviors will change (e.g., promise rejections will surface differently), and certain private or deprecated APIs are removed or changed. Projects should review the CHANGELOG and upgrade helpers before moving to 0.82.

This release marks an important inflection point for React Native: by committing to the New Architecture as the only supported path, the framework signals that it is moving forward without the weight of legacy design. For developers, this means the upgrade process may require more care (especially if using older dependencies or private APIs), but the long-term reward is a slimmer, faster, more coherent platform. The experimental Hermes V1 suggests that performance is becoming a key frontline concern, not just a nice-to-have. The React 19.1.1 upgrade and DOM node support further narrow the gap between web and native development, which is a strategic advantage for teams working across both platforms. For teams investing in React Native, this release sets a clear path forward: fewer legacy trade-offs, more predictable performance, and a tighter integration with the broader React ecosystem.