Skip to main content
A project is one app: its conversation, generated code, preview, and publishing settings. Your Fabricate account is the account you use to build. Accounts inside your generated app belong to that app’s users.

​
Start with one useful workflow

Open Fabricate and describe who the app serves, what they need to do, and what information it should remember. You can also explore templates for a starting design. For example, start a client portal with submitting and reviewing a request. Add invoicing or reporting after that first workflow works. See Write a project brief.

​
Work in the editor

  • Chat: request changes or ask questions. If you want an explanation without edits, say so explicitly. Messages use credits.
  • Preview: interact with the app and check the current work.
  • Code: inspect the files behind the interface.
  • Database: inspect preview data. This is not a view of the published database.
Return to an existing app from your app list rather than starting a new project for each change. Keep related work in the same conversation so you can describe the screen and behavior you are changing.

​
Review before publishing

A finished generation is a starting point for your review. Test a real action, refresh the page, and confirm that the result remains. If the app has accounts, test with two different users. Follow Test your app.

​
Share the version you choose

Use Publish when you are ready for a live address. Preview changes do not automatically update the published version. After changing code or environment secrets, publish again when the changes are ready. Publishing, visibility, and custom domains explain the available controls. Check pricing for current plan entitlements.

​
Keep a delivery record

For client work, record the agreed workflow, what you tested, the live address, and any known limitations. A preview screenshot does not establish that accounts, saved data, or payments work. Use the launch checklist before handing over the app.