Continuous Build
On this page
Continuous Build
🚧 Coming soon. The continuous build flow described here is not available yet. It builds on the App Builder and is rolling out in stages. Today you still run Prepare for Development and Build as separate steps — see App Builder.
Continuous build turns the three steps of going from idea to running app — plan → prepare → build — into a one-click happy path with a single review stop in the middle. You generate your whole plan with one button, review it, then kick off prepare-and-build as one continuous run and watch it finish.
The flow at a glance
- ⚡ Generate full plan — one click on your project Overview generates every plan section (personas, features, user stories, acceptance criteria, pages, database schema) in the right order. A progress strip shows each section filling in.
- Review your plan — the Overview becomes your review dashboard. Check the counts and the coverage panel, open any section to edit it. This is your one chance to course-correct before the app is built — and the cheapest place to do it.
- 🚀 Prepare & Build — when your plan looks right, one button runs everything to the finish: it prepares the development blueprint and then compiles, fills in, verifies, and (if you've connected GitHub/Vercel) deploys your app. You don't click anything else.
- Result — a deployed app URL, a GitHub repo, and/or a downloadable ZIP, plus a summary of what was built.
One review, by design. The review stop sits after planning on purpose. A plan is quick to fix; a finished build is expensive to redo. Catching a missing feature or wrong entity here saves a full rebuild later.
What "build succeeded" now means
Continuous build raises the bar for calling a build done. A successful build means your app:
- has every part filled in — no placeholder or stub files left behind, and
- actually compiles as a production Next.js build (not just a type-check).
If something can't be completed, the build stops and tells you where and why instead of quietly handing you a half-finished app.
When to use it (vs. the manual path)
| Use continuous build when… | Use the step-by-step path when… |
|---|---|
| You want the fastest route from spec to running app | You want to inspect or tweak each stage as you go |
| Your plan is in good shape and you just want it built | You're iterating on prepare/blueprint details |
| You're happy to review once, up front | You need to re-run only one stage |
The individual Prepare for Dev and Build steps stay available in the left sidebar — continuous build doesn't remove them, it adds a faster lane.
Before you start
- Plan / access: the App Builder is a premium feature. See Account & Billing.
- For a live deployment: connect GitHub and Vercel (and Supabase for the app's backend). Without them, you still get a downloadable ZIP. See App Builder for connecting accounts.
- A reasonably complete plan: continuous build checks your plan is ready before it proceeds. If it's too thin, it'll tell you what's missing.
Watching progress & what happens on failure
The run streams its progress on the Build page as a single strip across all stages (prepare → compile → fill → verify → deploy). If a stage fails:
- A transient hiccup (e.g. a provider timeout) is retried automatically a couple of times.
- A fixable issue in generated code is repaired automatically and re-checked.
- Anything it can't safely fix stops the run with a clear message naming the stage and the problem, so you (or support) know exactly what to look at. You can fix the underlying plan and re-run.