Designing an app · Lesson 9
From words to a manifest
Everything in this path can be written by hand. The app builder writes it from a description in plain words: it is an agent of the platform that knows the contract of the manifest, writes a draft, has it checked by the same validator you used in every lesson, and repairs what fails. Below are six of its real runs, from a census of 193 UK startups in November 2026, with nothing changed but the startups’ names left out.
Pick a run. On the left, the words it received; on the right, what it built; below, the problems found in its first draft, the repair request it got, and the final manifest checked now in your browser.
The loop
- Write. The builder reads the description and the contract, and answers with a whole manifest.
- Check. The validator — shape, references and safety, quality — lists every problem, word for word.
- Repair. The builder receives its own manifest and the list, and must fix exactly those problems and keep the rest.
- Test. The runtime serves the app; an automatic test opens every page, submits every form, starts every agent and fires every trigger against a simulated platform.
The numbers of the UK census
- 193 descriptions, 192 manifests. One request was declined by the model’s own safety rules, and left so.
- 101 valid at the first draft, 81 repaired in one round, 10 still failing. 182 of 192 valid in the end.
- The most common first-draft problem: an agent that would restart itself. 44 drafts; then unexpected properties (23) and placeholders nothing fills (11).
- 166 of the 182 valid apps passed the automatic test. The Italian census: 170 of 177 valid, 163 passed.
What stays human
The builder writes a correct manifest more often than not, and the validator makes sure an incorrect one is never served. What it cannot decide is whether the app is the right one: the sources it may use, the price, who should approve what. Those are choices — and the lessons of this path are what you need to make them.
What to take away
- A contract makes generation checkable. A manifest can be validated in full; a generated program cannot.
- Errors are information. The validator’s messages are precise enough for the builder to repair its own work.
- The test closes the loop. Valid is not the same as working: the app is opened and exercised before anyone uses it.
- Design stays a human job. The builder drafts; people decide what the app should be.
Next
One lesson is left: the summary of the whole model, and of what was built with it.
Lesson 10: Summary, what you can build →
← The whole path