Your design ships as a running product.
Describe a screen and Airbuild builds it — a real React frontend with a Python backend and its own PostgreSQL behind it. Then you keep editing the result directly in the preview, instead of annotating a picture of it.
Mockups stop where the product starts
A mockup answers what something should look like. It does not answer what happens when the form is submitted, where the record is stored, or who is allowed to see it. That gap is where design work goes to wait — for a sprint, for a developer, for a backlog slot.
Airbuild closes it in the same session. The screen you describe comes back as a working application, and the changes you make afterwards land in the code itself. There is no handoff document, because there is nothing left to hand off.
What you actually get
Not a prototype that looks finished — an application that is.
Design mode
Click any element in the live preview and change type, spacing, colour or copy. The edit is written into the real code, not into a design file somebody has to reimplement later.
Prototypes before code
Airbuild sketches the screens before it generates the application, so you judge layout and flow while changing your mind is still cheap.
Media generated in place
Images are generated and curated for the page they sit on, so a first draft can go in front of a client without a stock-photo hunt.
From screen to live site
The same path whether it is your portfolio or a client’s product.
Describe or bring it
Start from a prompt, or bring an existing site in by URL and let Airbuild take it over.
Shape it
Prototype first, then generate — and adjust in design mode until it reads the way you want.
Publish
One click to a subdomain or to your own domain. SSL and CDN are included.
Hand it over
Standard React and Python. Export it, or connect a GitHub repository and let a developer carry on.
What stays yours
Design work that ends in a file someone else has to rebuild is work done twice. Here the artefact is the product.
- Standard, exportable React and Python code — no proprietary runtime
- Every change is a real Git commit, with its history
- Your own domain, not a builder subdomain you cannot leave
- Free to start: 250 AI Tasks in your first month with a business email address
Questions designers ask
Do I have to write code?
No. You describe what you want and adjust the result in design mode. The code is there, it is readable, and it is standard React and Python — which is exactly what makes handing the project to a developer possible later. Nothing forces you to open it.
Can I import a Figma file?
Not today — a Figma plugin is on our roadmap, not in the product. What works now: describe the screen, bring a reference in by URL, or paste a screenshot, and then shape the generated result in design mode until it matches.
Is this only good for websites?
No. Websites work on every plan, including the free one. Applications with a login, a database and roles need the Web App Builder plan or above — the same design mode applies to them.
What if the client wants changes a year later?
The project is still there and the next change takes the same path: describe it, or edit it in design mode. If the client has moved on to their own team, they get the repository — the application runs without us.