Documentation · App Builder
Quickstart
Before you start
- You need an account in the Cloud Dashboard with the role developer or admin. The viewer role sees a read-only notice instead of App Studio.
- The first publish of an app creates its API key and stores it as a credential of your organization. That needs an admin of the organization. A developer can publish updates afterwards.
- To let your users pay, an admin connects a Stripe account (see Billing). You can publish without it: the app then shows that payments are not enabled yet.
Open App Studio at /dashboard/app-studio.
A real example
We built a booking and pre-visit app for a physiotherapy clinic with these steps. The co-pilot's proposal arrived about 2 minutes after we sent the description, and the app was live about 2.5 minutes after sending it. On the live app, after a patient's request, the background agent wrote the pre-visit summary and asked the clinic for approval in 28 seconds.
A design usually takes 1 to 3 minutes: longer for a larger app, with several agents, collections and approvals, and when the co-pilot makes a second pass to fix its first proposal.
Step 1: describe the app
On a new app the top of the page reads Describe your app. The co-pilot builds it. The input box shows the placeholder Describe your app — e.g. “a valuation report for real-estate agents, paid with credits”.
Type your description, or click one of the three cards under Start from an example (Property valuation report, Supplier due-diligence, Trip planner) and then Use this → puts its text in the box.
Here is the kind of description that works well:
An app for a physiotherapy clinic. Patients sign in, book a first visit from the free slots (45 minutes, Monday to Friday, 9:00–18:00) and fill in an intake form: the area that hurts, since when, pain from 0 to 10, previous treatments, and they can upload a medical report. A background agent reads the form and the report and writes a pre-visit summary for the physiotherapist: likely issues, questions to ask, red flags. The summary must be approved by the clinic staff before it is attached to the booking; patients never see it. Staff see all bookings in a table and the summaries waiting for approval. Patients see their own bookings. The first visit is paid per booking. Italian and English.
Then press Design the app (or Enter).
What the co-pilot needs to know
Write the description as if you were briefing a person. Cover these points:
| Point | Why it matters | Example |
|---|---|---|
| Who uses it | Becomes the roles and who sees which page. | "patients" and "clinic staff" |
| What they enter | Becomes the form fields and their types. | "pain from 0 to 10", "upload a medical report" |
| What the agent gives back | Becomes the agent's instructions and where the result goes. | "a pre-visit summary: likely issues, questions to ask, red flags" |
| What it keeps | Becomes collections. | "bookings", "summaries" |
| Who approves | Becomes an approval and an approvals page for that role. | "approved by the clinic staff" |
| What starts the work | Form submit, a record written, a schedule. | "when a booking is made" |
| How they pay | Becomes the billing section. | "paid per booking", "credits", "free" |
| Languages | Becomes metadata.langs. | "Italian and English" |
Also say what users must not see ("patients never see it"): it becomes the view and record rules.
Step 2: wait for the proposal
The button shows Designing… and the line The co-pilot is designing the app (usually 1–3 minutes). You can leave the page: the proposal waits for you. The co-pilot runs in the background. If you reload or come back within 30 minutes, App Studio picks up the same run.
Two things can happen instead of a proposal:
- If the first proposal has problems (it fails validation) or design warnings, App Studio sends it back to the co-pilot with the list and shows The proposal had N problem(s): the co-pilot is fixing them…. This second pass happens only once.
- If the co-pilot needs information, it shows The co-pilot asks: followed by its question. Add the answer to your description and press the button again.
Step 3: review and apply
The canvas shows the proposal, with a bar above it: The canvas shows the proposal: <app name>. New boxes have a green border and a new badge, changed boxes an amber border and a changed badge. Boxes the proposal would remove are listed after would remove:.
- Apply makes the proposal your app. The message reads Proposal applied — click the boxes to review, then
Save draft. A new app takes the slug the co-pilot proposed. The address now shows in the panel on the right,
for example
https://<slug>.webrobot.eu. - Discard drops it.
Nothing is saved yet. Click the boxes to check them:
- the Form box: the fields and which are required;
- each Agent box: its instructions (system prompt), model, turns and budget per run;
- the arrow from the form to the agent: the goal, the text the agent receives on each run;
- the Pricing box: how users pay;
- each Approval box: which role decides and what happens on timeout.
The right column shows the selected box under What the user sees, in the app's colours.
Step 4: save the draft
Press Save draft. The message reads Draft saved., or Draft saved — fix the problems before publishing. if the panel on the right lists problems in red. A draft with problems is still saved, so you never lose work. See Validation.
After the first save the slug belongs to your organization and the preview address exists.
Step 5: open the preview
Press Open preview. It opens https://preview-<slug>.webrobot.eu in a new tab: the saved draft, served by the
runtime, with a bar Preview — draft not yet published.
The preview is not public: sign in as an admin of the app. Agents do not run in the preview (a run answers that the agent has an inline profile and the app must be published first), payments are off, and data entered there is kept apart from the live app's data.
Step 6: publish
Press Publish. It is disabled while the draft has problems (its tooltip says Fix the problems first). If you have unsaved changes, App Studio saves them first.
The button shows Publishing…. When it is done the message reads Published v1 — live on https://<slug>.webrobot.eu. The status at the top of the page changes from draft to published v1.
If a step fails, the message names it, for example api key: …. See Publishing.
Step 7: try the live app
Open the address. Sign in with your email: the app sends a message with a sign-in link and a 6-digit code. Make a booking or run the form, and watch the agent's result arrive. For an app with approvals, sign in as a person with the approving role and open the approvals page.
Change it later
Open the app from the selector at the top (Open an app…) or from All apps. The heading becomes Describe a change. The co-pilot redesigns your app. and the button Propose change. Describe the change, for example add a follow-up visit of 30 minutes and ask for the date of the injury. The proposal shows only what changes. Apply it, save, and publish again: the version number goes up and the app's data stays.
Next steps
- App Studio: every part of the editor.
- Publishing: addresses, custom domains, republishing.
- Export to GitHub and phones: the code and the phone apps.
- The manifest tutorial at webrobot.eu/learn/manifest.