Build, preview, and refine

Build makes changes to your app. Use it when you know what you want to add, fix, or redesign.

Plan helps you work through an idea before implementation. Review the proposed approach, answer questions, and approve the work when it matches your intent. Planning and building are different stages; approving a plan is what moves the planned work into a build.

Check your credits and usage as you work. Do not assume a planning conversation is free simply because it does not change the app.

The project chat is where you describe changes and review progress. Give the page, action, expected behavior, and any design constraints. For bugs, include the steps that reproduce the issue and what you expected instead.

Explore the app while you build. The device controls let you check different screen layouts. Test buttons and forms instead of judging only the first screen.

If a preview has an error, give the project chat the error text and the action that caused it. After a fix, repeat the same steps to check the result.

Use the builder’s code view to inspect project files and make direct edits when you need precise control. Code changes and AI requests affect the same project, so review the preview after either kind of change.

You can begin with plain-language prompts. Familiarity with code becomes useful when reviewing complex logic, connecting external systems, or investigating an issue.

Open More actions → History in the chat panel to inspect available checkpoints and restore an earlier project state. Check that the selected checkpoint contains the version you want before restoring it.

Restoring project files does not necessarily undo changes made in an external database or third-party service. Clear chat is a separate action; use History when your intent is to restore the app.

Your development preview and your published app serve different purposes. Use Publish when you are ready to release your changes, then test the resulting live address. Follow the publishing guide.