App builder
The builder turns a plain-language description into a deployed app. It does not generate code from nothing: it starts from a tested business system or app starter that matches your idea, then customises it to your words. You get reliability from the starter and personality from the AI.
How a description becomes an app#
Understand the idea#
The builder reads your description and works out the business type, who the users are, the main screens and anything that must hold (a deposit, a role, a currency). If something essential is missing it asks one or two questions rather than guessing.
Match a starter#
Your idea is matched to the closest of the business systems and app starters. A dog-grooming salon lands on the appointment-booking system, a subscription box on the e-commerce starter, a members' community on the forum starter. If nothing fits well enough, the builder tells you and offers the nearest general-purpose starter instead of shipping something broken.
Customise#
On the instant path the starter is configured to your words: business name, services, prices, copy, colours and the pages your description implies. This path is fast and reliable, and it is what the Free plan uses.
On the full build, available on paid plans, the AI also writes custom screens and logic on top of the starter. If that deeper customisation fails for any reason, the builder falls back to the instant result of the same starter. A working app of the right kind always beats a broken custom one.
Check and repair#
Every build passes through automated checks before deployment: syntax, missing imports, undeclared dependencies, broken pages, a real render of each page. Problems are repaired automatically where safe, and the build is verified again. See Self-healing builds.
Deploy#
The app starts in its own isolated environment with its own database, at
https://mvp-<id>-<name>.preview.autoflowly.comand a short<name>.go.autoflowly.comalias for sharing. It begins as a private draft.
The live preview#
The preview opens signed in as you, the owner, so you can see the owner dashboard straight away. The toolbar lets you open the app in a new tab, copy the preview link, and jump to the dashboard.
While the app is a draft, the preview address is masked and the link you copy is a private one. After publishing the real address appears. See Publish, drafts and sharing.
Editing by chat#
Type what you want changed and the AI plans the edit, touches only the files involved, rebuilds and refreshes the preview. It explains what it changed and why. Typical edits:
- Copy and layout: "Shorten the hero text and put the booking button above the fold."
- Content: "Add a Senior cut service at 18 euro, Tuesdays only."
- Behaviour: "Require a phone number at checkout."
- Design: attach a screenshot, "Make it feel like this."
The editing path is protective:
- A change that would break the build is not deployed. The previous version keeps serving and the chat says which file failed.
- Before every edit the working files are snapshotted, so you can roll back. See Branches, versions and locked pages.
- Pages you lock are never modified by the AI, even if you ask for something that touches them; the planner routes around them and tells you.
New apps ship with labelled sample records so every screen has something to show. Replace them from the dashboard's Database tab before you share the app. The launch check reminds you.
Instant vs full build#
| Instant | Full build | |
|---|---|---|
| Plans | All plans | Starter, Pro and Business |
| What the AI does | Configures a tested starter to your words | Also writes custom screens and logic |
| Time | Usually under two minutes | A few minutes |
| Risk | Very low; the starter is known to work | Low; if it fails you get the instant result |
| Good for | Nearly every business and most product ideas | Ideas that need screens no starter has |
You can also request a full build later for an app that started instant: ask for a feature the starter does not have, and the builder tells you what it will do.
Models and fallbacks#
Autoflowly builds with Anthropic's Claude models by default and switches to OpenAI automatically when a provider is unavailable, so a build does not fail because one vendor has an outage. The Free plan uses the most economical capable model; Pro and Business use the most capable ones. You never pick a model yourself.
What gets generated#
A typical app has a React front end, a FastAPI back end, a PostgreSQL database with seeded tables, sign-in with owner, staff and customer roles, email templates, legal pages, and the hosting configuration. You can download the code of an app at any time from its dashboard.
Building from a document#
Bringing a full product requirements document and having a whole app built from scratch is in early testing and not yet generally available. Until then, paste the essentials into the chat: who it is for, the screens, and the rules.