Inside this guide
Start with a supported shape
Build self-contained, interactive web apps: project trackers, habit journals, invoice trackers and content planners. Use personal saved data, an invited team workspace for the same records, or private client spaces for a separate document per invited account.
A project supports up to 16 source files and 100 KB of source. Each saved data document supports up to 95 KB. An app can protect up to three independently recorded workflows. File-upload workflows use made-up samples of up to 8 KB, with the sample stored in the workflow and its backups. Start these recordings from an empty app; checks replay the upload, saved result and reopening on desktop and phone.
Know the service boundaries
The current builder does not provide custom public sign-up inside generated apps, arbitrary row permissions, multi-person client tenants, SQL servers, automatic file processing, external integrations, payment collection, background jobs or native mobile packages.
Generated apps run in a network-restricted sandbox. The brief check identifies unavailable services before generation. It offers an explicit narrower alternative for you to edit; it does not silently substitute one.
Make the brief concrete
- Personal tool
- “Track invoices I enter myself, filter unpaid invoices, and remember changes across visits.”
- Invited team
- “A job board for invited colleagues who all see the same records. Let viewers read and editors update.”
- Private clients
- “A project tracker where each invited client sees only their own projects and I can open each client’s space.”
- Portable app
- “A small content planner I can download with its source and run on my own host.”
Review before you share
Try the real workflow, check the phone layout, reopen saved records and review the generated text. Automated checks give specific evidence; they cannot decide whether the product meets your business needs.