Guide

From one sentence to a working app

Knowing what happens inside makes the wait a lot less puzzling.

Short answerWe read your sentence, write the code, run it for real in a space kept apart from every other project, and hand you a preview address only if it works.

We work out what to build

Your sentence tells us what kind of app it is, which screens it needs, and what it has to collect. Then the job is sized. Writing several files at once is a T1 job, adding or changing one feature is T2, touching up words and colours is T3. The size decides the price on the spot.

Big jobs ask you first

A T1 job costs 6 credits and shows you a card before anything starts. The card says what it plans to change. Nothing runs until you confirm. T2 is 2.75 credits and T3 is 0.5, and those go straight through. Either way, nothing starts while you are still guessing the price.

You pick a look before the first build

Six directions are offered. Colour, type and the shape of the first screen differ in each. You can add one line of your own, like “use bigger photos”. This step is why the same sentence gives two people two different screens.

It is written, then actually run

File names and code scroll past as they are written. The work happens in a space kept apart from other projects. When the writing is done it is run there for real — we check that the screen appears and the text is filled in, not just that the files exist.

If something breaks, it repairs itself

When a check fails, the AI reads the cause and rewrites. It tries three times. If that is not enough it moves up to a stronger model and tries twice more. If it still cannot fix it, it stops and puts everything back the way it was before. It never burns credits trying forever.

Then you keep talking to it

A preview address opens and you carry on from there. Every change that lands adds a restore point, and publishing runs nine security checks first. Across seven trades we ran ourselves, all seven reached a working screen in 221 to 616 seconds, averaging 370.

Common questions

Do I need to know how to code? Not a line. All you need is to describe what you want. If you later feel like opening the code, you can — reading it and editing it both cost nothing.

Who owns the app? You do. You can export the whole source, or push it to your own repository. We do not bury anything in it that only runs on our side.

What if the first draft is wrong? You do not start over. Say “make the first screen lighter” and it changes there and then. Restore points pile up as you go, so trying things is cheap.

Read next

Still stuck? Check the FAQ — if it is not there either, write to us and we will answer.