Validation is not a ritual where you ask three friends if an app sounds cool. It is the process of finding enough evidence to decide whether the idea deserves more time.
For a solo founder, the checklist has to be lean. You are not trying to write a research report. You are trying to avoid spending another week on a product with no buyer, no urgency, and no next step.
Validation should leave receipts: replies, notes, screenshots, calls, and decisions.
Validate the problem before the interface
A polished mockup can make almost anything feel plausible. Start with the problem. Who has it, when does it happen, what do they do today, and what does it cost them?
Ask for behavior, not compliments
Compliments are cheap. Look for behavior: a reply with a real story, a request to try it, a willingness to pay, a calendar booking, or someone sending it to a teammate.
Keep the proof attached
Validation evidence should live on the app record. If it is scattered across DMs and tabs, you will remember the emotional version instead of the actual signal.
Decide what would change your mind
Before building, write the threshold. Maybe it is five painful user stories, ten waitlist joins from strangers, or one paid pre-order. The number keeps the review honest.
App validation checklist
- Problem is described in a real user moment.
- Current workaround is known.
- At least one stranger gave useful evidence.
- First version is narrow enough to test.
- Validation threshold is written before the test.
- Decision is captured: build, research more, pause, or archive.
Keep going with MVP scope planner, user feedback tracker, app idea backlog.