What WAID Studio is
WAID Studio is a visual builder for WAID apps. It creates projects, previews
them live, and edits the settings that would otherwise mean hand-writing
waid.config.json. It is a companion to the CLI, not a replacement: a project
made in Studio is an ordinary WAID project, and waid build packages it the
same way.
Studio itself runs on the detir runtime rather than in a browser. That is deliberate. Running a demanding React app on detir is a parity test in its own right, so Studio is both a product and the thing that proves the runtime can carry real applications.
Studio is pre-release. It is on its own track, and these pages describe what it does today rather than what the design documents plan. Anything not listed here is not yet available.
What it does today#
| Area | What you can do |
|---|---|
| Projects | Create a project into your workspace, watch dependencies install, and open it |
| Preview | See the running app on a live preview server, at a chosen viewport |
| Identity | Set the display name, universal name and native URL scheme |
| Icon | Set the app icon and its background colour |
| Capabilities | Turn device capabilities on, with auto-detection from your source |
| iOS profile | Set the signing team, provisioning profile and deployment target |
| Agent | Describe a change in chat and have it written as React source |
The agent loop is code-first: it writes real React into your project rather than maintaining a separate visual document. What you get out is source you could have written by hand.
How it relates to the CLI#
Studio drives the same waid CLI you would run yourself. Creating a project
shells out to waid new and then npm install, streaming their output back
into the panel, so a failure you would see in a terminal is a failure you see
in Studio, named rather than swallowed.
That means the CLI must be installed and on your PATH. If it is not,
project creation reports it explicitly rather than failing vaguely.