React Native 0.84 Officially Released with Hermes V1, iOS Precompiled Binaries, and Advanced New Architecture Integration

The cross-platform mobile development landscape received a significant update today with the official release of React Native 0.84. Meta’s engineering team, alongside a robust open-source community of contributors, has rolled out a version packed with architectural modernizations, tooling upgrades, and performance enhancements. This latest iteration makes the Hermes V1 JavaScript engine the default runtime across both iOS and Android platforms, introduces precompiled binaries for Apple ecosystems out of the box, and aggressively strips away legacy framework remnants to cement the New Architecture as the definitive standard for enterprise-grade mobile applications.

Main Facts and Core Upgrades

React Native 0.84 arrives hot on the heels of version 0.82 and 0.83, continuing an aggressive trajectory toward codebase modernization. The most prominent headline of this release is the standardization of Hermes V1. Following an experimental opt-in period introduced earlier in the development cycle, Hermes V1 is now the mandatory default JavaScript engine. This next-generation evolution of the engine brings comprehensive enhancements to both the compiler and the virtual machine architecture, yielding measurable improvements in app startup times, memory footprint optimization, and overall script execution speed.

In tandem with the Hermes V1 rollout, iOS developers will immediately notice a drastic reduction in project build times. React Native 0.84 now ships precompiled .xcframework binaries by default. Historically, developers were required to compile the heavy React Native core from source during every clean build phase. By automating the download and integration of these precompiled binaries during the standard pod install lifecycle, developers can save critical minutes on every clean build, smoothing out continuous integration (CI) pipelines and local development loops alike.

Furthermore, version 0.84 introduces a strict requirement for Node.js v22.11 or later. This ecosystem-wide version bump enables the adoption of cutting-edge JavaScript features within modern React Native tooling chains, while simultaneously syncing the core framework with React 19.2.3. Developers are strongly encouraged to utilize version managers such as nvm or fnm to transition their build environments seamlessly before attempting upgrades.

Chronology and the Transition to the New Architecture

To understand the weight of React Native 0.84, it is essential to trace the chronology of Meta’s multi-year architectural overhaul. For years, the framework relied on the legacy "Bridge" architecture, which introduced serialization bottlenecks when passing asynchronous messages between the JavaScript thread and native platform threads.

The journey toward modernizing this paradigm began with the conceptualization of the New Architecture, centered around JSI (JavaScript Interface), Fabric (the new rendering system), and TurboModules. Following experimental phases in late 2023 and early 2024, React Native 0.82 made the New Architecture the sole runtime option, deprecating old paradigms.

Version 0.83 subsequently laid the groundwork for pruning obsolete code by introducing experimental flags. Now, in React Native 0.84, this pruning process shifts from experimental to mandatory. On the iOS front, the legacy architecture code is completely stripped from standard builds, reducing both overall binary bundle sizes and compilation overhead. On Android, a massive purge of legacy Java classes has taken place. Obsolete packages, bridge wrappers, and thread-unsafe debug listeners—such as LazyReactPackage, CxxModuleWrapper, and BridgeDevSupportManager—have been formally excised from the codebase.

While compatibility interop layers remain active to protect applications that have already migrated to the New Architecture, these sweeping removals signal the definitive closing chapter for legacy React Native patterns. Teams lagging behind in their migration schedules will find themselves forced to explicitly configure fallback flags or risk immediate compilation failures.

Supporting Data and Community Contribution Metrics

The sheer scale of React Native 0.84 underscores the vitality of its open-source ecosystem. According to release diagnostics, version 0.84 represents the culmination of over 650 discrete commits contributed by a global cohort of 95 developers. This collaborative output demonstrates sustained enterprise and community backing, with major contributions pouring in from independent maintainers as well as engineering squads at tech giants invested in cross-platform stability.

Accessibility has also received quantitative attention in this release cycle. Text components equipped with onPress or onLongPress interactive handlers now automatically inherit accessibilityRole="link". This programmatic adjustment guarantees that screen readers correctly interpret and announce interactive text strings across platforms. On the Android side, engineers resolved complex accessibility state leakage bugs tied to recycled views. By ensuring that isClickable and OnClickListener flags reset correctly during view recycling phases, the framework prevents assistive technologies from misreporting UI states to visually impaired users.

Additionally, web standards compliance has inched forward. The internal implementation of the global URL and URLSearchParams APIs has been heavily patched, introducing standard-compliant properties like hash, host, and pathname, alongside robust method handling for parameter manipulation.

Official Reactions and Industry Implications

While official statements from Meta’s core React Native team frame version 0.84 as a necessary leap toward operational efficiency, industry analysts and lead mobile architects have greeted the release with a mixture of enthusiasm and cautious pragmatism.

Engineering leaders have widely praised the default inclusion of precompiled iOS binaries and Hermes V1, noting immediate gains in developer velocity and runtime responsiveness. "Reducing the friction of clean builds on iOS has been a community wish-list item for years," notes one senior mobile infrastructure engineer. "By moving precompiled binaries out of the experimental phase, teams can shave significant time off their cloud build bills."

Conversely, the strict enforcement of Node.js 22 and the systematic removal of legacy Java and Objective-C classes mean that upgrading will not be a trivial, drop-in affair for large enterprise codebases. Teams maintaining heavily customized native modules that still rely on old bridge interfaces will need to dedicate engineering sprints to refactoring their native bridges to align with TurboModules and JSI standards.

Broader Impact and Future Outlook

The release of React Native 0.84 firmly establishes the framework’s identity as a modern, high-performance toolkit that no longer compromises its core architecture for backward compatibility. By burning the ships behind the Legacy Architecture and standardizing high-speed runtimes like Hermes V1, Meta is positioning React Native to compete directly with native application performance while retaining the unparalleled development velocity of JavaScript and TypeScript.

For projects looking to take the plunge, version 0.84 is live as the new stable release, while version 0.81.x has officially transitioned to unsupported status under the framework’s official support policy. Developers are advised to leverage the React Native Upgrade Helper alongside experimental community tooling, such as the upgrade-react-native AI CLI skill, to navigate breaking changes. Meanwhile, the Expo ecosystem has announced that React Native 0.84 will land in upcoming canary builds, setting the stage for Expo SDK 56 to inherit these modern architectural foundations in the near future.