Build your first app
From a blank screen to live: your first build step by step, and what to watch for.
From zero to live
- 1Write what you want
In the box on the home screen, describe your business: who uses it and what they do. e.g. "An appointment book for my salon where customers can book by phone number."
- 2Answer the questions
Smart Build asks up to 3 questions if needed. They sharpen the scope — answering them noticeably improves the result.
- 3Review the plan
You get a title, scope, screens and data model. You also pick the output language, accent color and model here. Nothing is built until you approve.
- 4Watch it build
The app builds in the background — you can close the page. It arrives full of realistic sample data and ready to use.
- 5Try it and refine
Actually use it in the preview. Say what you want changed in a sentence: "add a search box", "drop the price column".
- 6Publish
Hit Publish and the app goes live at its own address. Later edits don't touch the live version until you republish.
Interactive example: how a description becomes a plan
“An appointment book for my salon where customers book with their phone number”
An animation — it starts no real build and spends no credit.
Try it yourself: your first app in 10 minutes
Build a small app you can genuinely use, and publish it.
- 1In the composer, write a real need from your own work (not a made-up example).
- 2Answer the questions, read the plan and shrink the scope if needed.
- 3When it's built, add one record and delete one record in the preview.
- 4Ask for one change: "add a search box to the list".
- 5Publish it and open the link on your own phone.
You end up with an app that opens on your phone, stores data and can be shared — and you have seen the change loop first-hand.
Yes. Every generation is kept as a version; restore any earlier state with one click from version history. Your data is independent of versions — rolling back never deletes records.
Yes. A build belongs to your account, not a device; your draft, answers and choices live on the server.
Yes — the "Discuss" button in the composer. While it's on your app is NOT touched: no code change, no new version. If the conversation lands on a concrete change you get a ready build instruction, one tap into the composer.
Key takeaways
- Nothing is built before you approve the plan — shrink the scope there.
- A good description explains your business, not technology.
- Draft and live are separate; the live app never changes until you say so.
Related topics
Still stuck? Ask the assistant in the corner, or browse the FAQ.