react-native new architecture

In 2022, React Native dropped version 0.68. That release was a big deal because it introduced something called the “New Architecture.” At first it was optional, but now (as of 0.76) it’s on by default.

But why did React Native even need a new architecture in the first place?

The Old Days: Life With the Bridge

Before this, React Native used the Bridge to connect JavaScript and native code. Basically, JS would serialize data, send it over the bridge, and native code would pick it up on the other side.

That worked fine for a while. But if you’ve built anything non-trivial, you’ve probably seen the issues:

Long lists that lag or show blank placeholders while scrolling fast.
Animations that feel “off” or stuttery.
The app freezing when JS was doing too much at once.

Why? Because JS is single-threaded, and the bridge was asynchronous. If JS got busy, the UI just… waited.

That setup wasn’t really future-proof. So the RN team went back to the drawing board.

The New Setup

The new architecture removes the bridge and replaces it with JSI (JavaScript Interface). On top of that, there are two big changes you’ll hear about: TurboModules and Fabric.

Here’s the quick breakdown:

JSI → Think of it as JS talking directly to C++/native without the old JSON dance. Calls are faster, and less overhead means smoother apps.
TurboModules → The new way to load native modules. Instead of loading everything upfront, modules are pulled in only when needed. Faster startup, lighter memory use.
Fabric → The new rendering system. Written in C++, it lets React Native do things like concurrent rendering, better layout sync, and smoother animations. Basically, it makes the UI feel more “native.”

There’s also a revamped event loop that lines React Native up more closely with how React itself works on the web.

Why This Matters

Apps start up quicker.
You don’t pay the cost for modules you’re not using.
Animations and lists finally feel as smooth as they should.
It unlocks modern React features like Suspense and Transitions in RN.
It’s the direction the ecosystem is moving—most major libraries have already migrated.

Should You Care?

If you’re starting a new RN project, you’re already using the new architecture by default. If you’re working on an older app, migrating is worth it—you’ll eventually need to, since the bridge is on its way out.

In short: the New Architecture isn’t just a shiny upgrade—it fixes the core pain points we’ve all felt when building RN apps.