What you have when the first version is done

The pieces you can point at

When the first version is done, you should be able to point at a web app, not a chat transcript. SpinBuild writes three pieces: a frontend, a backend, and a private Postgres database for that project. You review each change as a diff and accept it before it ships. Starter is free and does not ask for a card.

Whether you code or not, the review is yours. You are checking that the change matches the web app you described.

What done looks like

• A frontend someone can use in the browser: the pages, the forms, the lists.
• A backend that answers those pages, so a reload does not forget the last action.
• A private Postgres for this project, so its data stays with this web app.
• A private preview you can click through before anyone else can.
• A publish step that puts the accepted version on your-app.apps.spinbuild.ai with HTTPS.
• An optional one-way push to a GitHub repository you own, so you have a copy of the code.

The limits that come with it

The live URL is the apps.spinbuild.ai address. A custom domain is not part of publish.

GitHub is a one-way push. Edits made on GitHub do not flow back into the builder on their own.

The result is a web app. It is not a native iOS or Android app.

The preview is private. SpinBuild does not include a built-in sign-in product for the people who use the published web app.

Those limits are part of the product. They are the same on day one and on the day you publish.

A sequence that keeps the first version honest

Describe the web app. Read the diff. Accept it or reject it. Click through the private preview. Publish when that path works. Push to GitHub if you want the code in a repository you own.

If the diff adds a screen you did not ask for, or stores nothing, reject it and send a narrower instruction. The project updates from what you accepted.

Start at spinbuild.ai. Questions about the product go to support@qyant.dev.