How to validate an app idea: the short answer
Validating an idea means gathering evidence that a specific group of people has a real problem, is already trying to solve it in some way, and would use (or pay for) your solution. It happens in four steps: define the problem and the audience, talk to potential users, test demand without coding, and test the solution with a clickable prototype.
The key is to trade opinions for behavior. A friend saying they 'think it's cool' is worth almost nothing. Someone leaving their email on a waitlist, agreeing to a 20-minute conversation or clicking an 'I want to try it' button is already a concrete signal.
In the next sections, you'll see each step in detail, with examples of what to do and what to avoid.
Step 1: Define the problem and the audience precisely
Before thinking about screens and features, write one sentence saying who suffers from which problem. For example: 'Freelance personal trainers waste time billing clients and rescheduling sessions by message.' If the sentence is vague, like 'people who want to get better organized,' your validation will be vague too.
Writing this down also helps you separate the problem from the solution. An app is just one possible way to solve it, and sometimes a spreadsheet or a messaging group already does the job well enough. Understanding this early keeps you from building something that competes with what people already do for free.
- Exactly who has the problem (profession, routine, age, context)
- How often the problem happens
- What the person does today to work around it
- How much time or money they lose because of it
- Why current solutions aren't enough
Step 2: Talk to potential users before showing your solution
Find 5 to 10 people in your target audience and ask for a short conversation. The goal isn't to pitch the app, but to understand how they deal with the problem today. Ask about the last time the problem came up, what they did and what was left unsolved.
Avoid leading questions like 'would you use an app that does X?' Almost everyone says yes to be polite. Questions about the past, like 'what did you do last time?' and 'have you ever paid for a tool for this?', reveal what people really do.
Write down the words they use. Those often become the copy on your website, in your ads and the names of your app's features. If the problem comes up repeatedly after a few conversations, that's a good sign. If every person describes something different, or says it isn't even a nuisance, it's worth rethinking your focus.
Step 3: Test demand without coding anything
Once the problem is confirmed, the next test is to see whether there's interest in a solution. There are inexpensive ways to do this without developing anything.
One is a simple page explaining your proposal, with a sign-up or waitlist button. You bring people to it through direct contacts, niche groups or a small ad budget, and watch how many actually sign up.
Another is the so-called manual MVP: you deliver the service 'by hand' to a small group, using messages, spreadsheets and forms. If your idea is a scheduling app, for example, you could book appointments for some professionals' clients manually for a few weeks. This shows what people actually use and where the process breaks down.
- Landing page with a waitlist
- Pre-registration form with questions about the need
- Manual service for 3 to 10 people
- Pre-sale or advance payment agreement, when it makes sense
- Follow-up conversations with the people who signed up
Step 4: Test the solution with a clickable prototype
Even with proven demand, a big question remains: does the app you imagine solve the problem the right way? That's where the clickable prototype comes in, a version that simulates the app's screens and flow without a working system behind it.
With it, you put the app in the hands of people from your audience and watch. Ask them to complete a task, like 'book an appointment' or 'record a payment,' and see where they hesitate, what they don't understand and what they expected to find. This often reveals unnecessary screens, missing features and confusing steps, all before you pay for development.
A prototype is also useful for aligning the idea with partners and investors and for getting a quote closer to reality, since the scope becomes visible. SKAD offers an AI-generated clickable app prototype with an approximate quote for R$ 99, and you can use it for exactly this kind of test before deciding whether to move forward.
Common mistakes when validating an app idea
The most frequent mistake is validating only with people who like you. Family and friends tend to support, not criticize. Look for people who fit your audience profile and have no reason to be kind.
Another mistake is putting too many features in the first version. The more the app does, the harder it is to know which feature creates value. Pick the main flow, the one without which the app makes no sense, and test only that.
It's also common to ignore negative signals. If nobody signs up, nobody agrees to talk, or tests show the flow is confusing, that isn't failure: it's cheap information. The real damage comes from learning the same thing after months of development.
- Asking 'would you use it?' instead of investigating current behavior
- Validating only with friends and family
- Starting with design or technology instead of the problem
- Trying to launch every feature at once
- Confusing likes and compliments with willingness to use or pay
How to decide: move forward, adjust or drop the idea
Before you start testing, define what would count as success. For example: 'at least 30 people from the target audience on the waitlist' or 'seven out of ten users complete the main task in the prototype without help.' The numbers are yours and depend on your market, but writing them down beforehand keeps you from interpreting the results in your favor.
If the criteria are met, you can move on to an MVP with a lean scope, already with a safer quote. If they're partially met, adjust the audience, the proposal or the flow and test again. If the problem doesn't exist or nobody cares, dropping the idea early is also a good outcome, because it preserves your money for the next attempt.
Frequently asked questions
How much does it cost to validate an app idea?
It depends on the path you choose. Interviews and a waitlist page can cost little or nothing beyond your time, and a clickable prototype usually costs far less than developing the app. The total varies with the number of tests and how much you invest in promotion.
Do I need a prototype to validate my app?
It isn't mandatory, but it helps a lot. Interviews and demand tests confirm the problem, while the prototype shows whether your solution is understandable and useful to the people who will use it.
How many people do I need to interview to validate an idea?
Between 5 and 10 conversations with people from the right audience usually reveal patterns. If the answers are still very different from one another, keep interviewing or reconsider how you've defined your audience.
What's the difference between a prototype and an MVP?
A prototype simulates the screens and flow but has no real system behind it. An MVP is a functional, lean version of the product that already delivers real value to the first users.
How do I know if my app idea is good?
An idea tends to be good when it solves a frequent problem for a well-defined audience that is already trying to solve it in some way and shows concrete interest, such as signing up, using the prototype or pre-purchasing.
Conclusion
Validating your idea doesn't eliminate all risk, but it replaces assumptions with evidence before you invest in development. Start with the problem, talk to the people who live it, test demand without coding, and let your audience try a prototype before you decide. If the signals are good, you move forward with more confidence and a clearer scope. If they aren't, you save time and money to bet on a better idea.