The Headlines
Over the past few months the same stories keep circulating: Shopify moving back to native, Coinbase reportedly rewriting its app in Swift and Kotlin, and Discord saying it is betting more on Rust. The question follows naturally: is React Native dead?
Then, this week, Expo's CEO Charlie Cheever revealed a new agent-native app framework called Exact, written in Rust. I'm a React Native developer, so this matters to me. This post is my take, prompted by [Simon Grimm's video on the topic](https://www.youtube.com/results?search_query=simon+grimm+expo+exact), which is well worth watching.
Why React Native Existed in the First Place
React Native was built on a simple bet: there is a giant economy of JavaScript and React developers, and they should be able to build mobile apps with the skills they already have. One codebase, multiple platforms, one team.
That bet rested on a principle: humans write the code, so the tool should fit the humans. That's the principle that has quietly changed.
What Changed: Humans Aren't Writing All the Code Anymore
Over the last year or two, a growing share of code is written by AI agents. And agents don't have a favourite language. They can write Swift, Kotlin, TypeScript, or Rust at similar speed, and they can maintain those repositories too.
That weakens the strongest argument for cross-platform frameworks, which was "we only have to hire and train for one language." If an agent can produce and maintain a native codebase for each platform, the cost of going native drops sharply.
A fair caveat on Shopify: reports say their rewrite took around 12 weeks with agentic coding, and part of the performance comparison was against an older React Native architecture. It's not an apples-to-apples verdict on modern React Native. But it does show what is now feasible.
What Exact Claims to Be
From the announcement and Simon's walkthrough, the key ideas are:
- ·Agent-native. It is designed for AI agents to use, not for humans to read.
- ·One codebase, many targets. Web, iOS, Android, Linux, Windows and macOS.
- ·Truly native rendering. No web views and no JavaScript bridge. It renders UIKit on iOS, AppKit on macOS, and the DOM on the web.
- ·A new UI language, "Contract". It's indentation-based and not especially pretty, and that is the point: agents care how it works, not how it looks. Its error messages are written to teach the agent the language as it goes.
- ·Logic in TypeScript or Rust, with a small set of agent commands to control the app, run tests, inspect the app tree, and manipulate an internal clock so time-based behaviour can be tested quickly.
The performance claims, such as beating Astro, Next.js or SvelteKit on the web and delivering higher FPS on native, are the author's own. It is pre-alpha, so treat them as claims until independently verified.
Simon gave it a spin by handing the repo's prompt to Claude Code, which produced a to-do app for web, iOS and macOS. Then he asked for new features and screenshots on every platform, and the agent handled the rest. His impression was that all three felt properly native.
Reading Between the Lines
The most interesting part isn't the framework itself, it's the target audience. React Native was built for the React community. Exact is built for agents.
That reframes a lot of things:
- ·Freedom is a liability for agents. React lets you do the same thing in a dozen ways, and anyone who has fought with
useEffectknows how that goes. A constrained framework with one obvious way to do things is easier for an agent to get right. - ·Feedback loops are a feature. Helpful error messages, deterministic tests, and a controllable clock are what let an agent verify its own work.
- ·Fewer codebases to maintain. Agents can write N native codebases, but one codebase to keep correct is still cheaper than N.
On Expo's side, my read (speculation, to be clear) is that this isn't a signal that Expo or React Native is dying. Expo is simply hedging and building for a world where the primary "developer" may be an agent. Expo and React Native are still going strong.
So Is React Native Dead?
No. But the reasons to choose it have shifted.
- ·Still strong: an existing React/TypeScript team, shared code with a web app, mature tooling and ecosystem, and a huge community. Expo's tooling keeps getting better.
- ·Under pressure: the argument that "one language saves us from learning two native stacks". Agents erode that advantage.
- ·Rising: frameworks and tooling designed for AI agents, and more Rust in the toolchain.
What I'd Tell Other Developers
1. Don't tie your identity to a framework. I wrote about this recently: with AI, switching stacks is far cheaper than it used to be, but only if you have the fundamentals.
2. Learn architecture, not just APIs. Boundaries, state, data flow, and testability matter in any framework, and they are what let you direct an agent well.
3. Keep an eye on the new tools, but don't rewrite for hype. Exact is days old. Wait for real production apps, Android maturity and ecosystem support before betting a product on it.
4. Stay the engineer in the loop. Simon asks whether you're comfortable shipping an app to the store without understanding what the code does. For me the answer is no. I want to be able to read, review and own what ships.
Closing Thought
Frameworks were built for people. We are entering a period where they'll increasingly be built for agents, and the people who thrive will be the ones who understand the fundamentals well enough to steer both. React Native isn't dead, but the ground under it is moving, and it's worth paying attention.
*Credit to Simon Grimm for the video that sparked this post. The claims about Exact come from its announcement and his walkthrough, and I haven't verified them myself.*