For several years, React Native has been in an architectural transition. The legacy system — a JavaScript bridge that passed messages asynchronously between the JavaScript thread and native code — was being phased out in favour of the New Architecture, which uses a direct C++ interface called JSI, a new renderer called Fabric, and on-demand native module loading via TurboModules.
That transition is now complete. React Native 0.82 has fully removed the legacy bridge. The New Architecture is not a beta feature or an opt-in — it is React Native.
What this means for existing apps
If your app was built on an older version of React Native and still uses the legacy bridge, you’re on a frozen track. React Native 0.81 and Expo SDK 54 were the last versions to offer legacy support as a migration bridge. From 0.82 onwards, upgrading requires migrating to the New Architecture — there’s no way around it.
For apps that haven’t migrated, this creates a hard ceiling: you can continue using the old version, but you won’t receive framework updates, security patches, or compatibility with newer iOS and Android APIs. In practice, that means growing friction with App Store and Play Store requirements over time.
The performance case for migrating
The New Architecture isn’t just a structural change — it’s a genuine performance improvement. The Fabric renderer reduces rendering time for complex lists by around 43%, and JSI eliminates the asynchronous message bottleneck that historically made certain interactions feel less native than they should. React Native in 2026 benchmarks significantly closer to native performance than it did two years ago.
What it means for new builds
New React Native projects should start on the New Architecture by default. This has been advisable since React Native 0.76, when the New Architecture became the default; from 0.82, it’s mandatory. Any serious development partner should be building on it as standard — if you’re commissioning a cross-platform build and your partner is still starting new projects on the legacy bridge, that’s a flag worth raising.
The practical question
If you have an existing React Native app: when you next have a meaningful development engagement, budget for the architectural migration. The longer you wait, the wider the gap grows between your version and current releases.
If you’re commissioning a new cross-platform build: ask explicitly whether your development team is building on React Native’s New Architecture. It should be a straightforward yes.
We cover cross-platform mobile development — React Native, Flutter, and when each makes sense — on our services page.