# Exact: A New 60 FPS Cross-Platform UI Framework from Expo

> Published 2026-11-10 · https://www.promptzone.com/wei_saito/exact-a-new-60-fps-cross-platform-ui-framework-from-expo-33jc

Expo launched **Exact** this week, a new open-source UI framework built for **consistent 60 FPS performance** across iOS, Android, and web. The project, [first highlighted in a Hacker News discussion](https://github.com/expo/exact) gaining 101 points, aims to solve jank in cross-platform apps by controlling the entire render pipeline.

> **Framework:** Exact | **Language:** TypeScript/React | **Targets:** iOS, Android, Web
> **Performance Target:** 60 FPS | **License:** MIT | **Status:** Experimental

## How It Works: A Declarative, GPU-Driven Pipeline

Exact is not another wrapper around native components. It implements its own **declarative UI layer** that compiles directly to Skia or native GPU commands, bypassing the traditional bridge used by React Native. This architecture eliminates serialization overhead and allows for **fully synchronous execution**.

The framework uses **Yoga from Facebook** for layout calculations, but then takes complete control of painting. Every UI element—from text to shadows—is drawn by Exact's own renderer. This gives developers pixel-perfect consistency across platforms but requires building interfaces with its specific set of primitive components.


![Exact: A New 60 FPS Cross-Platform UI Framework from Expo](https://promptzone-community.s3.amazonaws.com/uploads/articles/i35qbe4ln3a74qwcu3nd.jpeg)

## The Performance Promise and Current Benchmarks

The primary claim is **reliable 60 frames per second**, even during complex animations and gestures. Early testing and demos show this holds for basic to moderately complex interfaces. The performance gain comes from two key changes: removing the asynchronous bridge and using a **single, shared memory space** between JavaScript and the renderer.

Exact's own benchmarks, while preliminary, show a **~3x reduction in input latency** compared to standard React Native implementations for gesture-heavy interactions. The render cycle is consistently under **16.6ms**, the threshold for 60 FPS, in its curated test suites.

| Feature | Exact | React Native | Flutter |
|---------|-------|--------------|---------|
| Render Architecture | Direct to Skia/Native | Native Bridge | Direct to Skia |
| UI Language | Declarative (JSX) | Declarative (JSX) | Imperative/Declarative (Dart) |
| Performance Target | 60 FPS Guarantee | Platform-Dependent | 60 FPS Guarantee |
| Maturity | Experimental (v0.1) | Mature (v0.73) | Mature (v3.19) |
| Native Access | Limited (by design) | Full via Native Modules | Full via Platform Channels |

## How to Try It Today

Exact is in early development, but the repository includes a working **playground app**. To run it, you need Node.js, a React Native development environment, and iOS/Android simulators.

{% details "Setup Steps" %}
1.  Clone the repository: `git clone https://github.com/expo/exact`
2.  Install dependencies: `cd exact && npm install`
3.  Start the Metro bundler: `npm start`
4.  In a new terminal, run the playground:
    *   iOS: `npm run ios`
    *   Android: `npm run android`
    *   Web: `npm run web`
The playground demonstrates core components like boxes, text, images, and animations.
{% enddetails %}

The API is intentionally minimal at this stage. Developers define UI using Exact's components like `<Box>`, `<Text>`, and `<Image>`, styled with a familiar React-style `style` prop.

## Pros, Cons, and Community Reactions

The Hacker News feedback highlights both excitement and skepticism. Commenters praised the **ambitious technical approach** and the need for a smoother alternative. Others questioned the **ecosystem trade-off**, noting the difficulty of rebuilding a mature component library.

**Notable advantages:**
*   **Predictable high performance:** The architectural choices make 60 FPS a default, not an optimization target.
*   **Pixel consistency:** The same Skia-backed renderer on all platforms eliminates subtle platform rendering bugs.
*   **Developer experience:** Leverages TypeScript and a React-like mental model, lowering the barrier for web developers.

**Significant limitations:**
*   **Zero ecosystem:** No component libraries, navigation solutions, or form handlers exist yet.
*   **No direct native access:** This is a feature for purity, but a blocker for apps needing specific platform APIs.
*   **Experimental status:** The API is unstable and not ready for production applications.

> **Bottom line:** A promising performance-focused experiment that trades immediate utility for long-term render consistency.

## Who Should Use This (And Who Shouldn't)

**Exact is compelling for:**
*   **UI-intensive product companies** with the resources to build their own component primitives and who prioritize fluid interaction over quick feature delivery.
*   **Framework researchers** and developers interested in the future of high-performance JavaScript UI.
*   **Teams building visually rich, animated apps** (e.g., gaming UIs, creative tools) where frame drops directly harm the user experience.

**Avoid Exact for now if you:**
*   Need to ship a production app in the next 12 months.
*   Rely on any third-party React Native library for core functionality (e.g., maps, bluetooth, in-app purchases).
*   Are a solo developer or small team that benefits from the vast React Native ecosystem.

## The Verdict on Expo's Strategic Bet

Exact represents a foundational bet by Expo that the future of cross-platform development requires **ditching compromise at the render layer**. It’s a clean-slate reimagining that prioritizes performance and consistency over ecosystem compatibility. Its success depends entirely on Expo's ability to shepherd it from a compelling tech demo to a viable platform with a critical mass of components and tools. For now, it's the most interesting answer to Flutter's challenge from within the JavaScript world, offering a potential path for React developers to access similar performance without leaving TypeScript behind.