Getting started
Building your first app
What to write in the first box so that the first build already gives you something usable.
Write one sentence saying what the app does and who it is for. The more specific the sentence, the fewer rounds of fixing.
What works well
- “A site for a barber shop with appointment booking, a price list, and a personal area where a customer sees their own bookings”
- “A ticket system for a team: anyone can open a ticket, only an admin sees them all”
- “A product catalogue with a cart and an order form that is saved as a record”
What works less well
- “A beautiful website” — there is nothing there to derive pages or tables from
- “Like my competitor's” — we cannot see their site
What happens after you press build
The build runs five steps and reports each one as it goes: it plans the app, builds the shared frame that holds the navigation, builds the pages in parallel, checks that the code really runs, and saves a version.
At the end you have a live address. There is no “publish” to press — a build that passes the check goes live on its own.
A build that fails the check is not saved and not charged — including its automatic repair round.