The cross-platform development ecosystem is constantly evolving.
For years, React Native and Flutter have been among the most popular choices for developers building applications for multiple platforms.
Meanwhile, Kotlin Multiplatform has been gaining traction by offering another approach: sharing business logic across platforms while preserving native development when needed.
Now, the Expo team is exploring something different.
Meet Expo Exact.
An experimental framework that moves away from React Native's traditional architecture and introduces a completely different way of building cross-platform applications.
Let's explore what makes it interesting.
A Different Direction from React Native
Expo is widely known for its work around React Native, simplifying native development and providing tools that make building and maintaining mobile applications easier.
However, Expo Exact takes a different direction.
It is not another React Native abstraction, nor is it simply a new rendering engine.
Exact introduces its own programming model, without React, JSX, or the traditional React component lifecycle.
Instead, it uses a declarative UI language called Contract, combined with a runtime written in Rust.
The idea is to describe application interfaces and behavior in a structured way, allowing the framework to execute them across different platforms.
Understanding the Architecture
One of the most interesting aspects of Exact is its architecture.
Rather than relying on a single rendering technology everywhere, it uses platform-specific technologies.
For example:
- iOS: UIKit
- macOS: AppKit
- Web: DOM and CSS
Its runtime is written in Rust, while application logic can be implemented using TypeScript or Rust.
This creates an interesting separation between the UI description, application logic, and platform execution.
The goal is to provide a consistent development model without requiring every platform to use the same underlying UI technology.
Two Principles Behind Expo Exact
The project's README introduces three principles that help explain its direction. Two of them particularly caught my attention.
"Write the web, ship the platform."
This is an interesting architectural philosophy.
Developers describe layouts using CSS concepts, while the framework allows each platform to provide its own native controls, typography, colors, gestures, and accessibility behavior.
The goal is not simply to reproduce the same interface everywhere, but to make applications feel at home on each platform.
The second principle is even more interesting in the current AI landscape:
"An agent can do the whole loop."
This means an AI coding agent should be able to create an application, run it, inspect its interface, interact with it, control its clock, and execute tests.
In other words, the development workflow itself becomes part of the framework's design.
For a long time, frameworks have primarily been designed around how developers write and organize code. Exact suggests another perspective: what if the framework were also designed around how AI agents build, operate, and validate software?
The Growing Interest in Native Cross-Platform Development
This approach also reflects a broader movement in the mobile ecosystem.
Developers increasingly want to share code without necessarily sacrificing platform-specific capabilities.
Kotlin Multiplatform is an interesting example of this direction.
Instead of requiring developers to share the entire application interface, KMP allows teams to share business logic, networking, data layers, and other common functionality while maintaining native interfaces using SwiftUI on iOS and Jetpack Compose on Android.
With Compose Multiplatform, developers can also choose to share the UI itself.
These approaches demonstrate that cross-platform development doesn't necessarily mean building everything with a single UI framework.
There are different ways to achieve code reuse, and the best architecture depends on the application and the team's requirements.
Expo Exact explores another possibility within this evolving landscape.
Built with AI Agents in Mind
Perhaps one of the most interesting aspects of Exact is its approach to AI-assisted development.
Today, coding agents can generate components, implement features, and refactor existing code.
But generating code is only part of the development process.
We still need to run applications, inspect interfaces, interact with components, and validate behavior.
Exact introduces tooling designed to make these interactions possible.
Agents can:
- Build and run applications.
- Capture screenshots.
- Inspect UI structures.
- Simulate user interactions.
- Control application time.
- Validate application behavior.
This is particularly interesting because it moves beyond AI-assisted code generation.
It creates an environment where agents can participate in the implementation and validation process.
As AI becomes increasingly integrated into software development, frameworks designed around these workflows may become more relevant.
Does This Mean React Native Is Being Replaced?
Not at all.
Expo Exact is an experimental project, not a replacement announcement for React Native.
React Native continues to have a mature ecosystem, extensive library support, and a large community.
For applications already running in production, migrating to Exact would require significant architectural changes.
Existing React components, hooks, navigation solutions, native modules, and third-party integrations cannot simply be reused.
The same consideration applies to other cross-platform technologies.
Adopting a new framework is not just a matter of changing the runtime. It affects architecture, development workflows, integrations, testing, and long-term maintenance.
What Comes Next?
I find Expo Exact particularly interesting because it challenges some assumptions about how cross-platform applications should be built.
Kotlin Multiplatform has already demonstrated that sharing business logic while preserving native interfaces can be a compelling architectural choice.
Now, Exact introduces another perspective, combining a new UI model, a Rust-based runtime, and tooling designed for AI agents.
I wouldn't consider it a production alternative to React Native today.
But I would definitely keep an eye on it.
The future of cross-platform development may not be about finding one framework that replaces all the others.
It may be about having different architectural approaches for different needs, with AI increasingly becoming part of the development process.
And that's what makes projects like Expo Exact worth following.
What do you think about this direction for cross-platform development?
Top comments (0)