React Native 0.84 and Expo SDK 55: why existing apps no longer need a full rebuild

React Native 0.84 made the Hermes V1 engine the default and Expo SDK 55 added brownfield support, letting teams migrate an existing native app screen by screen. Reported code sharing is 80–95%.

The cross-platform question used to be framed as a rebuild: throw away the native apps, start again in React Native or Flutter. React Native 0.84 (February 2026) and Expo SDK 55 change that framing. Hermes V1 is now the default JavaScript engine, bringing faster execution and lower memory use, and the New Architecture, mandatory since 0.82 in October 2025, is fully settled.

The more important change for buyers is brownfield support. Teams can now add React Native screens to an existing iOS or Android app one at a time, rather than replacing everything in one go. Reported results are 80–95% code sharing between platforms and 20–40% faster feature delivery.

Why this matters commercially

A full rewrite means a long period with no new features, a large upfront bill and a risky switch-over. A screen-by-screen migration lets you start with the part of the product that changes most, often onboarding, settings or a checkout flow, and prove the saving before committing further. Native code stays where it earns its keep: camera, payments and performance-critical screens.

Flutter remains a strong alternative, holding an estimated 46% of cross-platform market share against React Native’s 35%. But for companies already running separate native apps, an incremental path is often the lower-risk choice.

Questions to ask your developer

So what

If you are paying twice for every feature on iOS and Android, you probably do not need a rewrite, but you do need a migration plan. BuildApps builds and migrates across iOS, Android and cross-platform projects. To scope a phased move, start a project.

← All research

More research.

GitHub Copilot adds Supabase, Webflow, Wix and five more connectors in public preview

GitHub Copilot now connects to eight more services, including Supabase, Webflow, Wix and Mixpanel, through verified MCP connectors in public preview. They join more than 25 existing ones.

Read ›

Gemini 4 Neon is generally available in GitHub Copilot, aimed at lower-cost agentic coding

Gemini 4 Neon is now generally available in GitHub Copilot for agentic coding. Google says its quality is close to Gemini 4 Carbon at a lower token cost per task.

Read ›

Claude Code 2.1.328 brings auto mode to Bedrock, Vertex and Foundry, and narrows /code-review to bugs

Claude Code 2.1.328 extends auto mode to Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud and Microsoft Foundry. /code-review now reports only bugs and CLAUDE.md violations.

Read ›

GitHub Copilot Evals: repeatable tests for AI agents, now in public preview

GitHub Copilot Evals lets teams write repeatable tests for AI coding skills, custom agents and MCP tools. It checks both the result and the path the agent took, and is in public preview.

Read ›

GitHub Copilot can now drive your browser: browser use enters public preview

GitHub Copilot browser use lets an AI coding agent control Chrome to debug web apps and run browser tests. It is in public preview across the CLI, the Copilot app, VS Code and JetBrains.

Read ›

Claude Code 2.1.327 refuses some symbolic links and lists broken setup in /status

Claude Code 2.1.327 tightens file and package permissions again and adds a /status list of broken agent, skill and hook settings. A short read for teams using AI coding tools on a live product.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work