Introduction
Building an app that looks and behaves consistently on phones, tablets, desktops, and the web remains one of the hardest problems in software engineering. Large teams with deep resources have wrestled with the same tension. Slack and Discord turned to Electron for their desktop clients. Microsoft's newer Teams app relies on WebView2. WhatsApp has experimented with both native and web-based code for Windows. The shared promise is obvious: write once, reach everywhere. But the reality is usually a compromise between development speed and platform-specific polish.
What Happened
The industry is shifting again. Shopify recently moved its mobile apps back toward native code. Discord's leadership has described rebuilding its desktop client using Rust and GPUI, with plans to share Rust code across mobile platforms. These moves suggest that even companies committed to shared codebases still want native performance and feel.
Into this landscape comes Exact, an early-stage project associated with Expo. Exact is designed to let teams build for multiple platforms from a single foundation while still using native interface controls. Instead of forcing every screen into a web view or a custom rendering engine, Exact maps its descriptions to the real UI toolkit on each host. On the web, that means the standard DOM and CSS. On Apple platforms, it uses UIKit and AppKit. Android and Windows are supported, though both are still maturing.
Exact centers on a declarative language called Contract. Developers describe the interface, its state, and how it should respond to user input. A compiler turns that description into instructions for the runtime. Business logic can be written in TypeScript or Rust. The project is also designed with AI coding agents in mind: an agent can inspect the interface, interact with controls, read state, and capture screenshots to verify its work.
Why This Matters
Cross-platform tools usually ask teams to choose between convenience and authenticity. Flutter draws its own widgets. Qt has served desktop developers for years. React Native bridges JavaScript to native modules, but it still carries its own abstraction layer. Exact attempts a different path: a shared declarative model that defers to native controls wherever possible.
Because Exact is pre-1.0, it is not ready for every production workload. Linux editing remains limited. Windows delivery and native control parity are unfinished. There is no packaged command-line interface yet, and the project does not use React or JSX. Rust compile times and binary size are also areas the team is actively improving. Still, the involvement of Expo and Charlie Cheever—veterans who helped make React Native practical for builds, cameras, sensors, and over-the-air updates—suggests the team understands what it takes to ship real mobile software.
Key Takeaways
- Exact uses a declarative language called Contract to define interfaces, state, and interactions.
- It targets native UI components on each platform, including UIKit and AppKit on Apple systems.
- Data logic can live in TypeScript or Rust.
- The framework is pre-1.0, with early-stage support for Android and Windows and limited Linux editing.
- It is built to work alongside AI coding agents that can test interfaces by inspecting and interacting with them.
- The maintainers are currently seeking issues and feedback rather than pull requests.
Conclusion
Exact is still young, and its authors are the first to say the details are far from finished. The project lacks a stable CLI, and several platforms remain works in progress. Yet the underlying idea—that teams can share code without abandoning native controls—addresses a genuine gap in modern app development. Developers interested in experimenting should try Exact on a real project, report reproducible issues, and watch how the framework evolves. Whether 2027 becomes its breakout year remains to be seen, but the direction is worth following.

Discussion
Join the conversation
Thoughtful reactions, questions, and follow-up ideas help shape the next story.