We have the web, desktop, and mobile. Each has its own conventions, tools, and rough edges. Keeping an app consistent across them is hard—even for the biggest teams.

Look at Slack, WhatsApp, Microsoft Teams, and Discord. These are products built by companies with enormous resources, yet their desktop apps have used web technologies to share more of the work. Slack and Discord have used Electron; the newer Teams desktop app uses WebView2. WhatsApp for Windows has also moved between native and web-based approaches.

The reason is understandable: a shared foundation gives teams more control over consistency and lets more developers work on the same code. Features can reach users across devices without maintaining every screen separately. If even these companies have to make that trade-off, the tooling gap is real.

Now we are seeing another shift. Shopify has moved its mobile apps back to native. Discord's CTO has said the company is rebuilding its desktop client with Rust and GPUI, while aiming to share Rust code with mobile. That work is still underway. To me, both moves show a desire for a better experience without giving up the value of shared code.

Flutter offered one answer: a shared UI across platforms, generally drawn with its own engine rather than the operating system's built-in controls. Qt has been doing cross-platform work for years too. Both are serious tools, but I have still been waiting for an answer that brings a shared UI, native integration, and a great development experience together.

And as more teams look toward native experiences, this is where I think Exact could be the right tool: a way to build across platforms from a shared foundation without giving up native integration. It is early, but the direction feels right.

What makes Exact interesting?

Exact introduces Contract, a small declarative language where you describe your interface, its state, and what happens when someone interacts with it. A compiler turns that description into a plan the runtime can use. Data logic can live in TypeScript or Rust.

On the web, Exact uses the real DOM and CSS. On Apple platforms, it uses UIKit and AppKit; other hosts take different approaches. The goal is a shared interface that feels right across platforms, with room for native integrations. Exact by name—but getting the details right on every device is still work to be done.

It is also built for a world where coding agents help build software. An agent can inspect the UI, tap controls, read state, and take screenshots. That gives it a way to test what it built instead of just declaring victory when the code compiles.

The gaps are real

Exact is pre-1.0 and changes quickly. Android and Windows can run apps, but both are still early; Windows native control parity and delivery are unfinished. On Linux, editing is still limited. There is no React or JSX layer, and there is no packaged CLI yet. Check the README for the current picture—it will change.

Rust build times and binary size matter too. I see them as problems to keep improving, not reasons to abandon the direction. Rust is gaining ground on the backend; seeing it help power a shared frontend runtime is exciting.

Why I trust this team

Expo and Charlie Cheever have spent years making React Native practical: builds, cameras, sensors, native integrations, and the developer workflow. Expo's over-the-air updates show that they understand the work that happens after an app ships. Native code changes still need a new build, and Exact has its own evolving update system. But that attention to developer experience is why I am paying attention.

Help make it better

It is tempting to build yet another 20%-finished cross-platform framework, post a demo, and move on. Experiments are valuable. But if we want an option that lasts, testing and improving a shared project can take us further.

Try Exact with something you actually want to build. Test it on the platforms you have. Look for bugs, inconsistent behavior, missing features, and things that do not feel right on the platform.

The maintainers currently ask for issues and feedback, not pull requests. Search existing issues first. If you find a new problem, explain what you did, what you expected, what happened, and which platform you used. A small reproducible Contract example or the prompt you gave an agent is especially useful. If there is an existing issue, add useful evidence there. Read the contribution guide before posting; its guidance may change.

This is the direction I have been waiting for. I am still calling it: 2027 could be Exact's viral adoption moment.

Read my original article.

Related: Desktop Apps Keep Getting Heavier.
Cover photo byChristopher Gower on Unsplash.