Turn a small idea into a working app
The discipline is not technical. It is refusing to build the second feature before the first one works.
What you will be able to do
Take one narrow job from idea to working, deployed application.
Before you start
- Completed the first website guide or equivalent.
- A repository under version control.
One job, stated in a sentence
If you cannot write what the app does in one sentence without using "and", the scope is too big for a first build. "Tracks which events I have saved" is a project. "Tracks events and manages my calendar and suggests things" is three projects wearing a coat.
Choose boring technology
For a first build, the smallest thing that works: a static page with local storage, or a simple server with one endpoint. Every dependency is a thing that can break and a thing you must understand.
Tests as the specification
Write down what correct looks like before building. With an agent this doubles as the instruction — a clear test is a clear specification, and a vague test is how you get code that passes and does nothing.
Step by step
- Write the one-sentence job.
- List three things a user must be able to do. Cut it to one.
- Write down what correct looks like for that one thing.
- Build the smallest version that does it, with help.
- Test it yourself, including the awkward inputs.
- Deploy it. An unshipped app teaches you less.
- Only now consider the second feature.
Build the smallest working version of this: a single page that lets me add an event title and date to a list, and shows the list sorted by date. It persists in the browser only.
Constraints: no framework, no build step, no dependencies. Semantic HTML, keyboard operable, works at 320px.
Correct behaviour: adding an item shows it immediately; reloading the page keeps the list; an empty title is refused with a visible message.
Write the code, then list what you did not handle.What good looks like
- It does one thing and does it correctly.
- It handles the empty and awkward cases.
- It is deployed and someone else has used it.
What it cannot do
- Local storage is per-device and can be cleared.
- Generated code needs review before it handles anyone else's data.
When it goes wrong
- Scope grew and nothing shipped.
- Return to the one sentence. Everything else is version two.
- Works for you, breaks for everyone else.
- You tested the path you expected. Ask someone else to use it without instructions.
Privacy and data handling
If the app stores anything about a person, you have data-protection duties even at small scale. Local-only storage avoids most of them, which is a good reason to start there.
Sources3 referenced
- HTML: structuring the web
MDN Web Docs · reference documentation · link checked 2026-09-06
- Guidelines for secure AI system development
National Cyber Security Centre · security guidance · link checked 2026-09-06
- Web Content Accessibility Guidelines 2.2
W3C · standard · link checked 2026-09-06
Links are checked at build time. If one has moved, tell us.
Read next
Build and deploy your first website
A real site, on a real address, built with help and understood by you. No framework, no build step, no prior experience.
Checked 2026-09-06
APIs, testing, accessibility and secure deployment
The four things that separate a demo from something you can leave running.
Checked 2026-09-06
Build a simple useful web app with a coding agent
A small deployed application that does one thing correctly, with tests you wrote and a review you performed.