Every team that ships to more than one platform knows the pattern. The web app comes first. Then a mobile app, written again in a different stack. Then a desktop app, usually a WebView wrapper that feels slightly wrong on every operating system. Three codebases, three release trains, and features that land on one surface months before the others.

WAID exists to stop treating native and web as separate rewrites.

The idea

With WAID you write one Vite and React application. From it you ship:

  • A real static website. Crawlable, linkable and cacheable. Not an application shell that renders nothing without JavaScript.
  • Native desktop builds.
  • Native iOS and Android builds.

The native builds are rendered by Detir, Splenta's GPU UI runtime, rather than wrapped in a WebView. You keep the development model your team already knows and get native rendering where it matters.

Why not just wrap the web?

WebView wrappers are attractive because they are cheap to start. The cost shows up later: scrolling that does not feel native, startup times that lag, and a rendering path you do not control. The application is a guest in someone else's browser engine.

Detir takes a different route. It is an AI-native GPU runtime that can render either HTML or its own typed intermediate representation. The same application gets a visual form for people and a machine-operable form for agents, from one description.

The agent angle

That last point is why WAID sits in the Splenta runtime layer and not in a generic tooling bucket.

Most of today's software stack assumes a human is looking at a screen. Layout is computed for eyes, and anything a machine wants to do has to be reverse-engineered from markup meant for people. Agents end up scraping pixels or guessing at a DOM.

When an application is rendered from a typed representation, an agent can work against what the application can actually do, rather than what it happens to look like. The same app is equally legible to a person and to an agent.

Adopt it on its own

WAID builds and ships applications today without requiring Arth, Splenta's language. Detir renders plain HTML as well as its own representation. The runtime layers are designed to compose, but each one solves a problem that stands on its own.

If your team maintains parallel web and native codebases, that is the problem WAID is built for. The WAID product page and the developer documentation are the best place to start.