How a build runs
Blueprints, phased building, and the check that proves each page actually works.
When you describe an app, the studio first asks a few sharp questions, then turns your answers into a blueprint — the pages, features, and data your app needs. The blueprint is built in phases, in a deliberate order:
- Data — the database tables and relationships the app needs.
- Shell — the design tokens, navigation, and footer every page shares, built once so pages agree with each other.
- Pages — one phase per page, each written and then screenshotted at desktop and mobile widths.
- Accounts — sign-up, sign-in, verification, and password reset, when the app needs them.
- Features — the remaining behaviour, plus a pass that checks no placeholder content survived.
Nothing is "done" just because it compiled
Before a build finishes, every page is opened in a real browser and judged on what actually rendered. A blank page, a server error, or a fatal console error sends the agent back to fix it and re-check. Pages that still fail are reported to you by name rather than quietly passed.
If a build hits an error it can't recover from, your progress is saved. Reopen the workspace and press Continue building to pick up where it stopped.
Still stuck on this?
Contact support →