Start by checking the idea, before you spend anything. Write it on one page, then talk to real people about the last time they had the problem. Once you have evidence, you decide what to build and who builds it.
This page cannot tell you your idea is good. No tool, score or guide can. What it can do is show you the order to check things in, so that you spend your time and money after you know more, not before.
I have an app idea, where do I start?
Start with real people, not with a developer. Check the idea before you pay anyone to build it.
This page is for you if you have an idea and nothing built. You may have no coding experience. You may be afraid of spending money on something nobody will use or pay for. In our study of 263 community posts and 47 jobs from founders at this stage, that fear is what comes up. It is our study's count, not search volume, and not every founder.
Here is the order. Each step links to where it is covered.
- 1Write the idea on one page
- 2Look at what people do now
- 3Find real people who have the problem
- 4Ask about the last time it happened
- 5Test one specific promise
- 6Write down what you saw
Evidence holds: decide what to build
Building: how to start building an app- Write the idea on one page
- Look at what people do now
- Find real people who have the problem
- Ask about the last time it happened
- Test one specific promise
- Write down what you saw
- Write the idea on one page. Who it is for, and the problem that keeps happening.
- Look at what people do now. The spreadsheet, the rival app, or nothing.
- Find real people who have the problem. Go where they already talk about it.
- Ask about the last time it happened. Not "would you use it?"
- Test one specific promise. Ask people to do something small.
- Write down what you saw. Then decide: test again, change the idea, or stop.
If the evidence holds, you move on to building. That is its own guide: how to start building an app.
What this page does not do: it cannot prove the idea will make money. It helps you find out what you can find out cheaply.
How do I know if my app idea is good?
You can't tell from your own head, or from how much your friends like it. You find out from what people do.
Some signs are weak. Some are strong. Here is the difference.
| Weaker signs | Stronger signs |
|---|---|
| People say it is a great idea | People use something repeatedly to solve the problem |
| An AI tool gives your idea a score | People pay, or agree to pay, for a fix |
| People leave an email address | People give you their time, again and again |
A compliment costs the other person nothing. A sign-up costs them a few seconds. Paying, or coming back to use something, costs them real effort. That is why those count for more.
Even the strong signs do not prove a business on their own. We do not give a pass mark, and you should be wary of anyone who does. You are collecting evidence to make a better decision, not to get a yes.
Founders ask this in their own words.
In April 2026 an aspiring app maker on r/SaaS asked which practical signal makes an idea worth building, which exercises helped, and where to find the first people to ask (the r/SaaS post, 22 Apr 2026).
The question has been around a long time: in October 2016 someone on r/startups asked how to test an app idea before building it (the r/startups post, 4 Oct 2016).
These are examples that the question exists, not a measure of how common it is.
How do I validate an app idea?
Do four checks before you test anything, cheapest first. Then write down what you saw.
Each step below is a few sentences and one thing to do.
Write it on one page. Who is the user? What problem keeps happening to them? Use this one-page idea sheet:
- Who it is for: one kind of person, described in a sentence.
- The problem: what goes wrong for them, and how often.
- What they do now: the workaround they use today.
- Your idea, in one sentence: what you would give them instead.
- What you are guessing: the things you believe but have not seen.
If you cannot fill in the first two lines, you are not ready to talk to anyone yet. That is useful to know.
See what people do now. What do people use today? A spreadsheet, a rival app, a pile of messages, nothing at all. If rival apps exist, read what their users complain about in reviews and forums. The complaints tell you where the gaps are.
Find real people who have the problem. Not friends and family. People who have the problem and do not owe you politeness. Look where the problem is already discussed: forums, groups, communities, the places your user spends time. Join in as a person who is learning, not as someone selling.
Ask about the last time it happened. Do not ask "would you use this?" Everyone says yes. Ask: when did this last happen? What did you do? What did it cost you in time, money or stress? What did you try? Listen more than you talk, and do not pitch.
About ten conversations is a practical place to start. It is a practice from our own working method, not a pass mark, and ten conversations do not guarantee demand. Stop when you are hearing the same things, or start again with a different group if you are not.
Write down what you saw. This is the step most people skip. Keep a short record with four parts: your assumption, the evidence for it, the evidence against it, and the next cheapest test. An example, to show the layout and not a real founder:
| Assumption | Evidence for | Evidence against | Next cheapest test |
|---|---|---|---|
| Tutors say they spend time chasing late payments | Some described a recent late payment and the messages they sent | Some said they drop that client and don't mind | Ask more tutors what they did the last time a payment was late |
Then make one of three decisions. Test again if the evidence is mixed: run the next cheapest test. Change the idea if you found a real problem, but not the one you guessed: rewrite the sheet. Stop if nobody has the problem enough to act. Stopping is a result, not a failure. You saved the cost of building it.
How do I test an app idea before building it?
Pick one specific promise. Put it in front of the people you talked to. Ask them to do something small.
A promise is one sentence about what your idea will do for them. "Never chase a late payment again" is a promise. "A platform for tutors" is not.
A simple sign-up page is one way to test it. The page says what you are offering, and the visitor says whether they want it. Be honest on that page about what exists and what the visitor is committing to. Never imply the app is built if it is not.
Know what the result means. A sign-up counts for less than a payment or repeated use. Someone who leaves an email address has said "maybe". Someone who pays, or comes back to use it, has said something stronger. So ask for the next small thing: a short call, a deposit, a place on a waiting list that asks a real question.
Whatever you see goes in your record from the last step.
What if someone has already made my idea?
A rival app is evidence that people want the problem solved. It is not a reason to stop.
If nobody has tried to solve it, ask why. Maybe nobody cares enough. If someone has, you have a head start: you can see what people like and what they complain about.
Look at three things. What do the rival's users complain about? What do they work around, with spreadsheets or extra tools? What does the rival not do for your person?
If you find a lot of rivals, narrow down. Pick one group of users or one job and do it better than the general apps. A smaller promise to a clearer person is often easier to test and easier to explain.
You are not looking for an empty field. You are looking for a gap that someone would act on.
Can AI tell me if my app idea is good?
No. AI can help you practise, but it cannot tell you what real customers will do.
Use it as a rehearsal partner. Ask it to play a customer so you can practise your questions before the real conversations, and to point out questions that lead the person towards the answer you want. That is useful.
But an AI role-play is rehearsal, not proof. It has no money to spend and no problem to solve. A score from an AI tool is the weakest kind of evidence you can collect. It knows nothing about the people you hope to serve.
Practise with AI. Then talk to real people. The conversations are what count.
What do I do once the idea holds up?
Decide what to build first, and how to get it built.
Building. The order for starting an app is its own guide: how to start building an app.
Choosing a route. The App Build Planner helps you see where your idea sits and what to build first. Its button is "Get your build plan".
Money. The App Cost Calculator gives you a market cost range. For the longer read, What an App Costs is the guide to what an app costs and why prices differ.
Two nearby questions. If you are wondering whether you can sell or protect the idea instead, read Can you sell or protect an app idea?. If you have no money or no coding experience, there is a page for that too: App idea, no money, no experience.
If you are asking whether you need a company to start, that depends on where you live. Ask your official business-registration office or an adviser.
What is the free Price and Scope Check?
You send us your brief. A person on our team reads it and sends you one page: what to cut, a cost range, how long it could take, and the questions to ask anyone who bids.
It is free. It is for someone who has checked the idea and is thinking about building.
It checks scope and cost. It is not proof that customers want your idea. Only the conversations and tests above can tell you that.
Questions.
I have an app idea, where do I start?
Check it before you spend anything. Write the idea on one page, find people who have the problem, and ask them about the last time it happened. Building comes after, once the evidence holds. No score or tool can tell you the idea is good; real conversations give you the evidence to decide.
How do I know if my app idea is good?
Look at what people do, not what they say. Repeated use and payment are strong signs. Compliments, AI scores and email sign-ups are weak ones. No single test proves a business, and nobody can give you a pass mark. You are gathering evidence to decide whether to test again, change the idea or stop.
How to start an app idea?
Make three moves before any building. Write the idea on one page. Hold about ten conversations with people who have the problem, as a practice and not a pass mark. Then run one small test of a single promise. Each move is cheap, and each tells you something the one before could not.
How do you validate an idea?
An idea is checked when real people describe the problem without being led, and then do something small about it. That could be using it again, paying, or giving their time. A compliment is not an answer. Write down what supports the idea and what goes against it, so you can judge fairly.
How to convert an idea into an app?
Check the idea first. Once the evidence holds, the next step is deciding what the first version includes and who builds it. That order is covered in our guide to how to start building an app. Turning an idea into an app before checking it is an expensive way to find out nobody wanted it.
How do I check if my app idea exists?
Search for what people use today to solve the problem, including spreadsheets, forums and rival apps. Then read what their users complain about. A rival is evidence that people want the problem solved, not a reason to stop. Look for the gap, such as one group of users the rival ignores.
What should I do if I have an idea for an app?
Do not start by learning to code or paying for a whole app. Those are the costly moves, and they come too early. Talk to the people you hope to help first. After that you have three options: test again, change the idea, or stop. Only then decide what to build.