React Native Windows 0.85: Exploring the New Architecture

Microsoft has made its decision. Version 0.85 of React Native Windows permanently closes the door on the old architecture, the one based on the asynchronous bridge between JavaScript and native code. For a project owner aiming for a mobile application with a future Windows extension, this October 24, 2026 announcement isn’t just a technical footnote for developers: it changes how you frame an MVP from day one. Here’s what you need to know, and how it affects your choices.

• React Native Windows 0.85 permanently removes the old architecture: it becomes mandatory for any new project.
• The new architecture, powered by Fabric and JSI, delivers measurable performance and responsiveness gains on Windows applications by eliminating asynchronous bridge latency.
• It reduces platform-specific code, a concrete advantage for projects planning a Windows extension after a mobile launch.
• Starting an MVP directly on this architecture avoids a costly migration later. On a first functional batch priced between €15,000 and €40,000 excl. tax, reworking the technical foundation afterwards can inflate the bill by 30 to 50%.
• Our agency supports project owners in the technical assessment and implementation of this architecture for their mobile and Windows applications.

Why a new architecture for React Native Windows?

The old architecture relied on an asynchronous bridge between JavaScript and native code, a well-known bottleneck for years. The new architecture eliminates it and connects both worlds directly via JSI, which changes the game for applications handling heavy UI or animations.

The Bridge worked by sending JSON messages in a queue, asynchronously. Every interaction between your JavaScript code and a native component (a scrolling list, an animation, a camera access) went through that queue. On complex interfaces, this created visible latency and stutters that users perceive without being able to name them. On Windows, where fluidity expectations match those of a classic desktop application, this flaw was a dealbreaker.

Microsoft therefore aligned React Native Windows with the trajectory set by the React Native team: an architecture that replaces this bridge with a synchronous interface. With version 0.85, there is only one option left.

What the old architecture couldn’t do

The old architecture blocked several now-common use cases: synchronous layout rendering, fine-grained management of React’s concurrent rendering, and above all genuine native code sharing across platforms without multiplying adaptation layers. Teams targeting deep native integration on Windows hit these limits, with workarounds sometimes fragile in production. A frequent mistake was believing a simple version upgrade would bypass the Bridge, when the bottleneck was structural: asynchronous JSON latency remained identical regardless of the SDK version number.

Fabric and the concrete benefits of the new architecture

Activating the new architecture brings three measurable results: a more responsive interface thanks to Fabric’s synchronous rendering, direct native access via JSI that reduces communication latency, and enhanced stability since Microsoft now concentrates all its maintenance efforts on a single architecture. Fabric replaces the old React Native rendering engine. It handles component layout and display synchronously, eliminating a good portion of the visual glitches observed before, a button reacting with a slight delay, a list jumping during scroll. On Windows, Fabric also enables cleaner support for React’s concurrent rendering, a feature that improves UI update management while the application continues responding to the user.

JSI, the bridge that replaces the Bridge

JavaScript Interface (JSI) does the job the Bridge did poorly: connecting JavaScript to native code without going through an asynchronous message queue. Direct result: less overhead, faster native calls, and the ability to call native code synchronously when needed. For an application making many round trips with native Windows APIs (files, notifications, system integrations), this is what makes the difference in real-world usage, not on paper.

Application performance: what concretely changes for the end user

Application performance isn’t measured in abstract benchmarks; it’s experienced in use: startup time, scroll fluidity, interaction responsiveness. The new architecture acts on each of these points because it reduces the number of steps between a user action and the application’s visual response. On a Windows application running in the background with multiple windows open, this difference is particularly noticeable.

An architecture that arrives just as the old one is removed isn’t a changelog detail: it’s the signal that the technical foundation of a project launched today must be designed for the next five years, not just to ship an MVP in six weeks without worrying about what comes next.

Should you adopt the new architecture today for your project?

Yes, without hesitation for any new project: React Native Windows 0.85 leaves no choice, the old architecture is gone. The real question concerns existing projects and the migration timeline, not whether to adopt the new architecture.

For a project owner starting a mobile MVP today with iOS and Android, this question may seem distant if Windows isn’t planned for several months or even years. This is a common reasoning error. React Native shares the bulk of code across platforms; the new architecture, meanwhile, structures how that code communicates with native, on all platforms, not just Windows. Starting a project on the old architecture today would mean building on a foundation already abandoned by its publisher.

The costly mistake: underestimating migration costs

Many project owners think they can “migrate later” without major consequences. In practice, an architecture migration affects custom native modules, third-party libraries not yet compatible, and sometimes entire sections of the build chain. For an enterprise React Native project, already costing between €40,000 and €120,000 excl. tax depending on complexity, a poorly anticipated architecture migration can add several weeks of debugging and native module rewriting, a budget that wasn’t planned initially because no one had assessed this risk upfront.

1. Assess third-party dependencies used and their compatibility with Fabric and JSI
2. Check the targeted React Native version (0.85.3 minimum for the new Windows architecture)
3. Start any new project directly on the new architecture
4. Plan a technical audit before any migration of an existing project
5. Test critical native modules in a development environment before production deployment
6. Allocate a dedicated budget margin for migration in the project timeline

What it changes for an MVP (Minimum Viable Product)

An MVP isn’t meant to last forever in its initial form, but it often serves as the technical foundation for the final product. A React Native MVP generally ranges between €15,000 and €40,000 excl. tax. Starting this MVP directly on the new architecture doesn’t cost more, it’s now the default behavior of the tools, and it avoids a migration bill that lands at the worst possible time: right after fundraising, when you need to scale fast.

How the React Native Windows new architecture influences cross-platform development

It further unifies React Native behavior across iOS, Android, and Windows, since all three platforms now share the same Fabric/JSI foundation. For a project targeting a Windows extension after a mobile launch, shared native code grows, and behavioral discrepancies between platforms shrink.

Contrary to what is sometimes read, React Native was never a simple “write once, run everywhere.” Each platform retains its specificities, native components, and UI constraints. What the new architecture changes is the depth of the common foundation: with a single bridge based on JSI across all platforms, custom software development teams write native modules that behave more predictably from one platform to another.

Cross-platform development: where it really simplifies, where it changes nothing

It simplifies sharing business logic and common native modules. It does not simplify UI adaptation: a Windows application retains its own expectations regarding navigation, windowing, and keyboard shortcuts, and you must continue adapting the UI component by component. The frequent mistake is believing the new architecture eliminates this adaptation work, it doesn’t; it just makes the technical foundation more solid for doing it.

Toolchain: Visual Studio 2026 and .NET 10 change the equation for agencies

Version 0.85 imposes a renewed build chain: Visual Studio 2026 and .NET 10 become prerequisites for compiling a Windows application with the new architecture. For an agency managing multiple projects in parallel, this means updating development environments, revalidating CI/CD pipelines, and training teams on this toolchain before offering Windows to clients. It’s a real but one-time adoption cost, not to be confused with a recurring cost per project.

React Native Windows architecture overview: quick comparison

The following table compares the old and new React Native Windows architecture on criteria that matter to a project owner: communication bridge, rendering, and official status since version 0.85.

Concretely, any Windows project started with React Native Windows 0.85 inherits the new architecture by default, with an up-to-date toolchain as an entry condition. The old asynchronous bridge model is discarded, eliminating JSON serialization latency between native and JavaScript threads.

An enterprise React Native project costs up to 8 times more than an MVP

A React Native MVP costs between €15,000 and €40,000 excl. tax, an enterprise project between €40,000 and €120,000 excl. tax, and a complex platform with backend exceeds €120,000 excl. tax. The gap between the low end of the MVP range and the high end of the enterprise range illustrates the impact of functional scope on budget.

Starting with the new architecture from the MVP stage avoids a later migration cost that can represent 30 to 50% of an enterprise project’s initial budget. Fixing the architecture mid-course, when native modules are already coupled to the old bridge, is the most expensive mistake we see at the agency.

Based on your situation: which approach to adopt?

A startup launching a mobile MVP with a Windows roadmap within a year

For this profile, the main criterion is avoiding technical debt that would block the planned Windows extension. The recommendation: start directly with React Native Windows 0.85 and the new architecture, even if Windows isn’t a priority at launch. Shared native code and the current toolchain avoid a rewrite when the Windows extension arrives, since the old architecture simply no longer exists to fall back on. A React Native MVP ranges between €15,000 and €40,000 excl. tax, which fits launch budgets.

An SME that already has a React Native application in production on mobile

Here, the key criterion is service continuity: no question of interrupting an application used by customers to migrate urgently. The recommendation: audit dependencies and native modules before any update to 0.85, then plan the migration in stages, with non-regression tests. The cost of this upstream debugging avoids a production outage after a rushed update. An enterprise React Native project costs between €40,000 and €120,000 excl. tax, which includes this type of audit and progressive migration.

A business software publisher targeting a pure Windows desktop application, with no mobile need

For this profile, the determining criterion shifts: mobile cross-platform has zero value; only deep integration with the Windows ecosystem matters (windowing, shortcuts, system APIs). The recommendation differs from the two previous cases: React Native Windows remains relevant for development speed, but custom software development closer to native may be preferable if Windows integration needs are very deep and specific. A complex platform with backend exceeds €120,000 excl. tax, a threshold to anticipate if native integration takes precedence.

Working on a project like this? See our dedicated page: react native agency.

FAQ on React Native Windows and the new architecture

What is React Native Windows new architecture?

The React Native Windows new architecture is the technical foundation based on Fabric and JSI that replaces the old asynchronous Bridge. Mandatory since version 0.85, it connects JavaScript and native code directly via a synchronous interface, eliminating the JSON message queue that caused latency in the previous architecture.

How to migrate to React Native Windows new architecture?

Migration involves auditing native modules and third-party dependencies, updating to a recent React Native version, then activating Fabric and JSI in place of the Bridge. Each custom native module must be tested and, if necessary, rewritten to work with the new architecture. Planning a technical audit before any migration of an existing project is essential.

What are the benefits of React Native Windows new architecture?

The benefits include a more responsive interface thanks to Fabric’s synchronous rendering, direct native access via JSI that reduces communication latency, and enhanced stability since Microsoft concentrates all maintenance efforts on a single architecture. It also reduces platform-specific code, a concrete advantage for projects planning a Windows extension after a mobile launch.

When will React Native Windows new architecture be stable?

The new architecture is already stable and mandatory since React Native Windows version 0.85, released in October 2026. Microsoft has completely removed the old architecture in this version, meaning the new architecture is the only option for any project using version 0.85 or later. It is production-ready and no longer considered experimental.

The removal of the old architecture in React Native Windows 0.85 isn’t just a version number going up: it’s the signal that an entire technical foundation has shifted, and it must be factored in from the very start of framing a mobile project that targets Windows tomorrow. If you’re carrying a mobile application project with this cross-platform ambition, let’s discuss it during a technical scoping session: our team evaluates with you the most relevant architecture for your MVP, with a quote provided after scoping.