The most expensive app is one nobody wants. Validation is how you find out early, while changing your mind is still cheap. You do not need a big budget or months of research, just a few honest conversations and something people can react to.
Validating an idea is not asking friends whether they like it. Friends say yes. Validation means finding evidence that a specific group of people has the problem, cares enough to change what they do today, and would use (or pay for) your solution.
The goal is not certainty. You will never have that. The goal is to replace your biggest guesses with evidence, cheapest test first, before you spend real time and money.
Every idea rests on a few assumptions. "Gym owners struggle to keep members coming back." "They would message members through an app if it were easy." "Members would open it." Write yours down and circle the one that would kill the idea if it were wrong. Test that one first.
If you cannot name the person who has the problem, start there. A vague audience makes every test fuzzy.
Before showing anything, have short conversations with people who should have the problem. Ask about their past behavior, not their opinions about the future. "Tell me about the last time this happened" gets you facts. "Would you use an app that..." gets you politeness.
The strongest early signal is not enthusiasm, it is effort. People who have the problem badly are usually already doing something about it, even something clumsy. They keep a spreadsheet, juggle three apps, send the same text every week, or pay someone to handle it. That workaround is your real competition, and it tells you how much the problem is worth to them.
Weak signals are compliments, "I'd totally use that", and likes on a post. Strong signals cost the person something: time to talk to you, an introduction to someone else, a sign-up to try the first version, or a deposit. Collect strong signals. Politely ignore the weak ones.
If nobody has a workaround, the problem may be real but not painful enough to change habits. That is worth knowing before you build.
Once the problem looks real, test whether people understand your solution. Mockups (pictures of your main screens) are ideal for this. They are quick to make, easy to change and good enough for people to react to.
Show the main screen and ask: what is this for? What would you tap first? What do you expect to happen? If people cannot tell what the app does from its main screen, fix that before you build.
Comparing several directions helps too. In Co-Create you can see your screens drawn up to ten ways side by side, as close variations or new styles. Show two or three to the people you interviewed and ask which one they would rather use, and why. You learn about their taste and about what they think the app is for.
Avoid explaining the mockup before people look. Your explanation is exactly what real users will not get.
Mockups test understanding. Only a working app tests behavior. When people get the idea and want it, build the smallest version that does the core job for real, then see whether they come back to it.
Keep it brutally small. One job, no settings screens, no admin panel. A booking idea needs a way to see open slots and book one. It does not need loyalty points.
This is where AI app builders save the most time. In Co-Create, the plan you have already shaped becomes the build: approve the core items, and a live preview of the real app appears after each build. Because nothing is coded until you approve it, the first version stays as small as you mean it to be.
Send the working preview to the people you interviewed and a few you have not met. A web link works on any phone with nothing to install, which removes the biggest barrier to trying something new.
Co-Create's preview is meant for exactly this stage. It is a real, public link, rebuilt after every change, with a daily visitor limit so it suits testers rather than a full launch. When you are ready to open the doors, Go Live gives the app its own clean address.
Set your decision rule before you look at the results, so you do not talk yourself into anything. For example: "If at least half of testers complete the task, and some use it again unprompted, I keep going."
In Co-Create, changing course does not mean starting over. Edit the plan, approve the changes, or roll back to any earlier point and take a different path.
Interviews cost only your time. For the mockups and the working preview, Co-Create is $80 a month or $700 a year after a 7-day free trial, and every new trial starts with 25 build credits. Building uses credits at about $1.25 each. A small first version uses fewer than a finished app, which typically takes 10–30 credits to build and polish.
If the idea passes, nothing is thrown away. The validated version is the start of your real app, and you can download its source code anytime.
Start free. Talk it through, answer a few questions, pick a design and watch it build.