WebRobot

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

The numbers of the UK census

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

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