Skip to content

Analysis · Mobile development

Expo Exact: a native framework without React, built for AI agents

On 9 November 2026, Charlie Cheever, co-founder of Expo, unveiled Exact: a framework written in Rust, without React, that builds a native app for the web, iOS, macOS and Linux from a single source, and that an AI agent can build, run and test on its own. How it differs from React Native, and why it is too early to use it in production.

  • Published 18 November 2026
  • By Mehdi Najeddine
  • 10 min read
Modernist painting: at her drafting table, a woman draws a blue circle; on the wall, four frames shaped like a phone, a tablet, a laptop and a monitor repeat the same circle

Key takeaways

  1. Exact is a preview released by Expo under the MIT license: a framework written in Rust, without React or JSX.

  2. The interface is written in Contract, a new declarative language that uses CSS names; the logic, in TypeScript or Rust.

  3. One source, a native app per platform: DOM and CSS on the web, UIKit and AppKit on iOS and macOS, its own renderer on Linux.

  4. It is not a React Native replacement at this stage: no published release, no API stability, and Expo keeps supporting its framework.

the web runtime: one ES module that drives the browser's DOM and CSS
~20 KB
identical operations for an agent to drive the app on every platform
10
platforms: web, macOS, iOS and Linux work; Android and Windows are early
4 + 2
published releases: you work from the GitHub repository, whose API changes daily
0

The announcement

What Expo unveiled on 9 November

Exact is a new app framework, written in Rust. Charlie Cheever, co-founder of Expo, unveiled it on 9 November 2026 in a post titled “A preview of Exact”. The expo/exact repository was created on GitHub on 2 November, under the MIT license.

The idea: write an app once and run it natively on the web, macOS, iOS and Linux, with Android and Windows still early. According to the README, no platform uses a webview or a JavaScript bridge for the interface, and no app JavaScript runs before the first frame.

Charlie Cheever calls it an “Agent Native” framework. It assumes that much of the code will be written by AI agents, and gives them what they need to build, run, see and test the app with no one watching.

Figure 1From a single source to a native app per platform
  1. You write

    • app.contract

      The view, the state and the actions, with CSS layout names.
    • app.ts or a Rust crate

      Data and business logic, behind a typed boundary.
  2. Exact compiles

    • The Contract compiler

      Syntax, types and analysis, then a “plan”: tables and bytecode.
    • A baked plan

      Constant data is evaluated into it: the first frame needs nothing else.
  3. Each platform draws

    • Web

      One ES module over a runtime of about 20 KB, with the browser's DOM and CSS.
    • iOS and macOS

      UIKit and AppKit views, and the system's controls.
    • Linux

      Exact's own renderer, on the GPU or the CPU.
    • Android and Windows

      Early: Exact's own renderer.

Based on the README of the expo/exact repository (accessed 18 November 2026).

Contract

A new language for the interface, designed for agents

The interface is written neither in JSX nor in React components, but in Contract, a small declarative language created for Exact. It looks like Python (indentation matters), it is strongly typed, and its layout and property names are CSS's.

Contract describes the view, the state and the actions, but performs no I/O. No JavaScript in the view, no loops and no await in actions: data crosses a single typed boundary, into TypeScript or Rust. A simple HTTP request can even be declared in Contract itself, with no data code.

Figure 2A complete app in Contract: one state, one action, one view
app.contractContract
component App
  state count = 0
  action increment
    count = count + 1
  view
    button press=increment
      text `Count: ${count}`

Example from the Exact README. It names no color, font or size: each platform draws its own button.

The compiler explains its refusals. Instead of making the agent read a long manual, it returns targeted messages that say what to write instead: below, use font-size, the web's name, rather than size. Charlie Cheever sees it as one of the cheapest ways to make an agent read only the docs it needs.

Figure 3A compiler refusal that says what to write
Terminal
$ cargo run -q -p contract -- build app.contractapp.contract:4:5 [type-assign] `count` is `number`, cannot assign `string`app.contract:7:23 [lower-unknown-attr] `text` has no attribute `size`; `size` is spelled `font-size` here, the web's name (LLP 1017 §8.1)

Example from the Exact README.

Comparison

How it differs from React Native and Flutter

React Native and Flutter also build apps for several platforms from one source. The Exact README details what sets it apart, and acknowledges what it still lacks compared with these two proven frameworks.

Figure 4Exact, React Native and Flutter, point by point
Comparison of Exact, React Native and Flutter
CriterionExactReact NativeFlutter
Writing the interfaceContract, a dedicated declarative language; logic in TypeScript or RustReact components, in JavaScript or TypeScriptWidgets in Dart
LayoutCSS, with the browser as the referenceYoga: flexbox with different defaults (a view is a column and does not shrink)A layout model of its own
Rendering on iOSUIKit views and the system's controlsNative viewsIts own widgets, with a Cupertino set that imitates iOS
WebThe DOM and CSS, with a runtime of about 20 KBThrough the separate React Native for Web libraryDrawn into a canvas
MaturityPreview: no published release, interfaces that change dailyVersioned releases, years of production use, a large communityVersioned releases, years of production use, a large community
EcosystemPure-JavaScript packages in data modules; React Native and Flutter plugins do not worknpm and React Native librariespub.dev

Based on the “Compared with React Native and Flutter” section of the Exact README.

AI agents

A framework an agent can build, run and test on its own

The same ten operations drive the app on every platform, from the web to a physical iPhone, through a single script:

  • tree
  • screenshot
  • tap
  • type
  • state
  • layout
  • logs
  • clock
  • prefer
  • perf

The agent controls the clock. In a driven app, time only moves when the agent decides: instead of waiting for an animation to finish, it advances the clock, then reads the result. Its screenshots and state reads no longer race timers.

Tests are scripts of these operations. An app.test.contract file runs unchanged on every platform, and every tool reports in a form a program can read. Agents are also asked to log the friction they hit: these notes only go to Expo if the project allows it.

Figure 5The agent drives the app and decides when time moves
Modernist painting: a human hand and a mechanical arm reach toward a small glowing rectangle on a table, beneath a clock without numerals

Performance

Promising numbers, published by the author

The following measurements were published by Charlie Cheever in his announcement post. They have not been independently verified, and none of them compares Exact with React Native on mobile: on the web, the comparison is with Astro, SvelteKit and Next.js; on iOS, with UIKit and SwiftUI.

Figure 6Web: Largest Contentful Paint (LCP)

Shorter bars mean faster pages. Median of 5 agent-built apps, Lighthouse mobile settings.

  • Exact802 ms
  • Astro
  • SvelteKit
  • Next.js
Show the data as a table
Pokédex benchmark on the web, median of 5 agent-built apps
FrameworkLCP (ms)JavaScript (KiB)Performance score
Exact8020100
Astro8050100
SvelteKit1,15036100
Next.js2,01414299

Source: Charlie Cheever, “A preview of Exact”, 9 November 2026. Pokédex benchmark proposed by Nolan Lawson.

Neck and neck with Astro, well ahead of Next.js. To build that same app, agents took a median of 8.1 minutes with Exact, against 10 minutes with Next.js and 6.6 minutes with Astro, at a cost of $3.48 ($3.22 with Next.js) and 914 lines of code against 1,591. Charlie Cheever acknowledges that a static site in Astro is still cheaper and faster to produce. The README adds that on the RealWorld benchmark, Exact's runtime was up about 300 ms before the React server-rendered build had hydrated, with 26 KB of code against 81 KB.

Figure 7iOS: scrolling smoothness with live updates

Longer bars mean smoother scrolling. iPad Pro M1, 120 Hz display.

  • UIKit
  • SwiftUI
  • Exact120.0 fps
Show the data as a table
Scrolling on iPad Pro M1 at 120 Hz, frames per second
TechnologyHeavy list (fps)With live updates (fps)Late frames per secondExtra-heavy feed (fps)
UIKit119.696.10.3113.0
SwiftUI92.168.412.3106.5
Exact119.9120.00.0117.6

Source: Charlie Cheever, “A preview of Exact”, 9 November 2026.

Figure 8An iOS app before and after moving to Exact
time until the splash screen goes away
÷ 4.8
from 1.92 s to 0.40 s
time until lists show
÷ 2.2
from 1.93 s to 0.88 s
memory used after launch
÷ 2.9
from 106 MB to 36 MB
app size on the simulator
÷ 4.2
from 151 MB to 36 MB

Source: Charlie Cheever, 9 November 2026. The post names neither the app nor the technology it used before Exact.

Maturity

What already works, and what is still missing

Figure 9A promising product, still under construction
Modernist painting: on wooden scaffolding, a woman fits a panel marked with a red circle onto a structure that is still unfinished

Expo says it plainly: Exact is a preview. Charlie Cheever calls it “pre-alpha”, and the README states that, by design, there is no API stability, no backwards compatibility and no migration guide. There is no published release either: you work from a checkout of the repository.

Already available

  • Web, macOS, iOS (Simulator and devices) and Linux, from a single Contract source
  • CSS layout (block, flex, grid), gradients, shadows, glass effects, SVG and Canvas 2D
  • Transitions, animations and gestures (pan, swipe, pinch)
  • Virtualized lists, inputs, images, video and the camera
  • Data in TypeScript or Rust, SQLite, Keychain and OAuth sign-in
  • Signed over-the-air updates, and embedding in an existing Swift app (ExactKit)

Not yet

  • Android and Windows are early; Play Store submission remains the publisher's work
  • No JSX or React, and no compatibility with React Native or Flutter plugins
  • Code updates in production are still partial
  • No packaged command-line tool and no devtools interface
  • No published release, no API stability and no migration guide

Source: the “What works today, and what doesn't yet” section of the Exact README.

Our view

What it changes for a bank or a large company

The points below are our analysis, not announcements by Expo.

  1. Not for your production apps today

    A preview, an unstable API, no published release: nothing that suits a banking app with stability, security and compliance requirements.
  2. Android, the blocker in Morocco

    Android accounts for about 73% of mobile devices in Morocco, according to StatCounter (October 2026), and it is one of the two platforms still in early form. Until that is solved, Exact cannot power a consumer app in Morocco.
  3. React Native remains the sensible choice

    Expo keeps supporting its framework built on React Native, which is growing faster than ever according to Charlie Cheever: more than 17 million downloads in the week of 2 to 8 November 2026. Exact is also meant to work with Expo's cloud services.
  4. The real signal: frameworks written for agents

    A constrained language, a controlled clock, the same tests on every platform, errors that explain: Exact shows what a development tool designed first for AI agents can look like. That is the trend to watch, beyond this framework.
  5. The web becomes the reference again

    CSS layout, a real DOM on the web, native controls elsewhere: a single design system, described with CSS names, could serve both the website and the apps.
  6. A new language to learn

    Contract is new and not in the training data of AI models, as Charlie Cheever himself points out. Teams, and their agents, will have to learn it, with no existing pool of developers.

Recommendation

What to do now?

  1. Migrate nothing

    Keep your production apps on React Native and Expo: Exact has neither a published release nor API stability.
  2. Isolate business logic

    Separate business logic from the interface, in TypeScript with no dependency on React: it pays off today with React Native, and it is the part a future framework could reuse.
  3. Think of design in CSS

    Describe your design system with CSS names and its layout model: it serves the web, and it is Exact's foundation.
  4. Try it on a prototype

    To form your own opinion, prototype a non-critical screen, on the web or on iOS, ideally with an agent: that is the intended use.
  5. Measure for yourself

    Check startup, memory and smoothness on your own devices, including entry-level Android phones, rather than relying on the author's numbers.
  6. Watch three milestones

    A first published release, a stable API, and Android out of early form.

FAQ

Frequently asked questions

What is Expo Exact?

An app framework from Expo, unveiled as a preview on 9 November 2026. Written in Rust and without React, it builds a native app for the web, macOS, iOS and Linux from a single source, and an AI agent can build, run and test it. Android and Windows are still early.

Does Exact replace React Native?

No, not at this stage. Expo says its framework, built on React Native, is not going away and that it will keep supporting it. Exact is a preview, with no published release and no API stability.

Can you reuse React components or React Native libraries?

No. Exact has no JSX or React layer, and React Native and Flutter plugins do not work. Data modules can, however, import npm packages written in pure JavaScript.

What is Contract?

The declarative language in which you write an Exact app's interface: the view, the state and the actions. It uses CSS layout names, performs no I/O, and data logic is written separately, in TypeScript or Rust.

Is Exact ready for production?

No. Expo presents it as a preview: no published release, no API stability, no backwards compatibility and no migration guide. Android and Windows are still early.

What license is Exact released under?

The MIT license. The code is on GitHub, in the expo/exact repository.

About the author

Mehdi Najeddine

Founder & Director of VOID

VOID designs and builds mobile apps with React Native and Expo, including for banks and fintech companies.

Choosing the right technology for your mobile app?

We help you choose between React Native, native development and new frameworks like Exact, based on your platforms, your teams and your constraints.