A minimum viable product, or MVP, is the smallest version of your app or platform that lets real users complete the one job your product exists to do. Its purpose is to learn quickly and cheaply what customers actually want before you invest in everything else.
Step 1: define the one job
Write one sentence that describes the problem you solve and for whom, for example “help clinic patients book and pay for appointments on their phone.” Every feature in your MVP should serve that sentence.
Step 2: list everything, then cut hard
Write down every feature you imagine. Then mark each one: must have for a first customer, nice to have, or later. Be strict. Admin dashboards, advanced settings and social features can almost always wait. Payments, sign-up and the core workflow usually can’t.
Step 3: design the core journey
Map the few screens a user needs to get from opening the app to finishing the job. Test a clickable prototype with five to ten real people before writing production code. You’ll find the confusing steps cheaply.
Step 4: build in short, visible steps
Develop in weekly increments you can try on your own device. Weekly demos keep the scope honest and surface problems while they’re still small.
Step 5: measure, then decide what’s next
Launch to a small group, track whether people complete the core job, and talk to them. Let real behaviour, not the original feature list, decide what you build next. A focused MVP gets you to that learning in weeks or months instead of years.