App Builder / Practical guide
Build and verify a small browser application
App Builder creates a browser document with a live preview, code editing, project conversations and publishing. Start with a narrowly scoped working flow rather than a long list of screens that cannot be tested.
A useful workflow
- Use New project for separate work, or choose a starter in Templates. Templates run locally without an AI generation request.
- Specify the user, pages, data fields and one central action. Select a builder model; AI generation uses workspace credits.
- Test the preview, including navigation, empty input, long text and mobile layout. Use the Issues panel and follow-up prompts for concrete corrections.
- Keep a ZIP backup. Sign in to publish to /p/your-slug; open the published URL and test it separately from the editor preview.
Examples and why they help
Build a habit tracker with habit name, daily checkboxes, add/delete controls and browser persistence. Include an empty state and show a weekly total.
Names a complete testable flow and an explicit persistence boundary.
Build a Three.js obstacle game with start, restart, score and touch controls. Include a loading error if the 3D library fails.
Makes game controls and dependency failure part of the acceptance criteria.
Before you rely on the result
- A preview that looks complete can still contain placeholder actions; test every visible button.
- Browser storage is not a shared database. Real accounts, payments and shared data need separate service configuration.
- Projects and conversations are saved in this browser. Clearing site data can remove them; export important work.
Questions about App Builder
Can I publish without signing in?
You can build and preview as a guest. Publishing uses an account so published documents have an owner.
Do I get a custom subdomain?
The current publisher serves documents at /p/your-slug. Custom domains and individual subdomains are not provided by this workflow.
Is generated code production-ready without review?
No. Test behavior, accessibility, third-party resources and security. Hash-routed pages in a single document do not have separate server-visible URLs for search indexing.