← Back to all posts

Watch Your App Being Built

Watch Your App Being Built

The preview is the app, not a picture of it

When you describe an app to Kreova, the panel beside the chat is not a progress bar and not a screenshot taken at the end. It is the app itself, on a real address, updating while the build is still running. The homepage arrives while you are looking at it. The photos land. The colours change under you when the styling pass goes through.

That matters for one reason. A build you can watch is a build you can redirect, and redirecting it in the first minute costs you a sentence. Finding out at the end costs you the build.

Here is what three minutes of it actually looks like.

A real build, minute by minute

We asked for a website for a home bakery. Kreova asked four questions before starting: the bakery's name, how customers should get in touch, the visual direction, and whether there were real menu items and prices yet or placeholders would do for now. Warm bakery, white and deep berry pink, an elegant serif, placeholders on the menu for now.

Then it went. Times are from the moment the build began.

0:17 - the database. Not the homepage. Before there is anything to look at, Kreova works out what the site needs to remember.

0:18 - five photo searches, all at once. elegant layered cake with berries close up. baker decorating cake in kitchen. They go out together rather than one after another, and each one appears in the preview as it happens.

0:32 - six photos chosen. They land on the preview as cards, tilted, for a few seconds each, so you see what it picked before the page that uses them exists. If one of them is wrong, this is the cheapest moment in the entire build to say so.

1:22 - the stylesheet. Styling styles.css. This is where the colours you asked for become real. Kreova went back through it twice in the following ten seconds, checking its own work against the direction we had given it.

2:21 - the homepage starts arriving. This is the part worth watching. The page is not written and then revealed; it is shown as it is written, growing for about a minute. Hero, then the story, then the cakes, then the contact panel. Sections that are built to fade in as a visitor scrolls are shown anyway while the page is being typed, so you are never looking at a nav bar above two empty bands, and the real animation comes back once the page is finished.

2:40 - the behaviour. Wiring app.js. The menu, the scroll effects, anything that has to answer a click.

2:48 - Kreova looks at its own work. It opens the finished homepage in a real browser at full width and checks it the way you would: images that did not load, errors in the console, a layout that has collapsed. You get the screenshot in the chat as well.

3:15 - ready. Twenty-two steps, none of them failed.

One sentence, in your language

Above the preview there is a single line saying what is happening right now, rewritten as the work moves along. It is deliberately not a log. It will not show you a file path, a table name or the name of a tool. From the bakery build:

Choosing images for the hero and featured cakes based on orientation and visual appeal.

Applying the chosen color scheme to the hero text and overall site design for cohesiveness and visual appeal.

A developer does not need those lines and would rather read the steps. Everyone else needs exactly this. The steps are underneath if you want them, and the whole build record downloads as a text file whenever you ask for it.

Everything you can do while it is still running

Say something without stopping it. Type into the chat while the build is running and it goes to the build in progress; Kreova picks it up at its next step. Make the pink darker can land while the stylesheet is still being written rather than after.

Stop it. One button, at any point. Everything already written stays.

Point instead of describing. Three ways, and all of them attach to your next message so you never have to put a location into words: click an element in the preview to attach it, drag a box over any part of the page to attach a picture of that region, or simply highlight text on the page.

Change the words yourself. Text edits on the page do not need a build at all.

Look around. A dropdown for any page in the site, and three widths: desktop, tablet at 768px, phone at 390px. Kreova also knows which page you are currently looking at, so "this heading is too big" is not ambiguous.

The arrow beside a checkpoint

Every time Kreova finishes a coherent piece of work, it writes a checkpoint into the chat. Beside each one is a small arrow.

Click it and Kreova undoes what that checkpoint changed, and leaves everything after it alone. Undo is an ordinary build, not a hidden mechanism: the request is written into the chat in plain words, so you can see exactly what was asked for and read back what it did.

Why we build it this way

The finished app is the same whether you watched it being made or not. What changes is when you find out.

Almost every expensive correction in a build is cheap in the first ninety seconds. A photo you would not have chosen. A pink that is too bright. A page heading somewhere you did not mean. All of them are visible long before the build is finished, and all of them cost one sentence while it is still moving.

So the preview is not a loading screen with pictures on it. It is the part of Kreova you are meant to use.