Lesson 5 — From Idea to a Working MVP
An idea is not an app. The gap between "I want to build X" and a working X is where most projects stall — usually because the first version is too big to ever finish. This lesson is about closing that gap with a repeatable process. It is the process you will use in the capstone.
Start with the MVP
MVP stands for Minimum Viable Product — the smallest version of your idea that still delivers its core value. "Minimum" because you cut everything non-essential. "Viable" because it must still actually work and be useful. An MVP is not a worse product; it is a focused one.
The reason to start here: a small first version can actually be finished, tested, and shown to a real person — fast. Everything you learn from that real version then guides what you build next. A giant first version just stays unfinished.
Practice cutting scope
The hardest part of an MVP is leaving things out. Try it — sort each feature into the first version or "later."
This activity needs JavaScript enabled. The lesson below still covers everything.
The build lifecycle
Once you know your MVP, every small app follows the same seven stages. You will recognize Lesson 3's and Lesson 4's habits inside them.
Idea and audience
Name what you are building and who it is for. "A tip calculator, for someone splitting a restaurant bill." One sentence.
Define the MVP
Write the one core thing the first version must do. Put every other idea on a separate "later" list and set it aside.
Plan in small steps
Break the MVP into an ordered list of small, checkable steps. Each step should be something you can finish and look at.
Build with an AI assistant
Work through the steps one at a time, using the Lesson 3 habits — give context, scope each request, read what the AI actually changed.
Test it
Use the app yourself. Does the core thing work? Try it on a phone-sized screen. This is the Lesson 4 verifying habit applied to a whole app.
Iterate
Fix what testing exposed, then improve. Now — and only now — you pull items off the "later" list. Each round is small.
Ship it
Get it in front of a real person. An app no one uses is not finished — it is just a file. Shipping is also how you learn what to iterate on next.
The lifecycle is a loop, not a line: shipping and testing feed straight back into the next round of iteration.
Quick check
This activity needs JavaScript enabled.