DEV Community

Mosmox Studio
Mosmox Studio

Posted on Originally published at mosmox.com on

How to Validate a Mobile App Idea Before Development Begins

How to Validate a Mobile App Idea Before Development Begins

The most expensive mobile product mistake is not a technical bug. It is spending months building a feature that does not solve an important problem. Validating an idea before writing code helps separate real demand from a team’s assumption, and it costs a fraction of reworking a finished app.

This article describes the process we go through with clients during discovery: from framing the problem to a minimum experiment with a success criterion defined in advance. It does not guarantee success, but it shows honestly where the development budget should go.

Start with a problem, not features

Describe the problem in one sentence: who has it, when it appears, and how people solve it today. For example: “Owners of small coffee shops manually compile weekly supplier orders in a messenger and regularly get quantities wrong.” That sentence can be tested; “people need a convenient business app” cannot.

Then speak with people from the audience and ask about the last real instance, not a hypothetical “would you use this?” Behavior is usually more reliable than intent: almost everyone will agree an idea is interesting, but only some will remember the last time they faced the problem and how much time or money it cost. Rob Fitzpatrick describes this approach in detail in The Mom Test.

What to validate: four dimensions

Dimension Interview question Strong signal Weak signal
Frequency and impact “When did this last happen? What happened next?” Weekly, with concrete loss of time or money “Sometimes,” with no example
Current alternatives “How do you solve it now? What does it cost?” Spreadsheets, manual work, paid workarounds “I don’t, but it would be nice”
Moment of habit change “What would have to happen for you to try something new?” A specific event or trigger General agreement with no conditions
User language “How would you describe this to a colleague?” Repeated words across respondents Terms the team invented

In our experience, 8–12 interviews with one clearly defined group are usually enough for answers to start repeating. If the picture is still chaotic after 12 conversations, the segment is most often defined too broadly.

A few practical interview rules: 30–45 minutes, one interviewer and one note-taker, recording only with the respondent’s consent. Recruit where the audience already discusses the problem: professional communities, topic chats, customers of an adjacent service. Right after each conversation, write down three quotes and one concrete case — a day later the details fade and your notes will contain only your interpretations.

What the YouTube Go story teaches

The YouTube Go story, written up by Google Design, shows why field research matters. The work began in 2014 with interviews in India, later expanded to Indonesia and Nigeria, and lasted about two years.

The team did not assume users simply wanted “lighter video.” An early concept with low-quality video — key frames with audio — was rejected by participants: they wanted a decent picture even with limited data. Instead, the real problem turned out to be opaque costs: people could unknowingly burn through a 100 MB data pack in one sitting. So the app showed a preview of key frames and the file size before streaming or downloading — for example 2, 5, or 12 MB depending on quality.

The key lesson: the right problem (“I don’t know how much data I will use”) was different from the obvious assumption (“I need worse but lighter video”). That kind of discovery is exactly what pre-development validation is for.

A minimum experiment, step by step

Before building an app, you can test a one-page description, a prototype of the core journey, a manually delivered service, or a waitlist. Here is the sequence we recommend:

  1. Write the hypothesis. “If [audience] gets [solution], they will [action], because [reason].”
  2. Define the success criterion before starting. For example: at least 40 waitlist sign-ups from the target segment in two weeks, or 7 of 10 prototype test participants completing the core journey without hints.
  3. Choose the cheapest format that answers this specific hypothesis (see the table below).
  4. Run it and do not change conditions mid-test, or the result becomes impossible to interpret.
  5. Record the decision: continue, change the hypothesis, or stop. No decision is the worst outcome.
Format What it tests Typical timeline (studio experience)
Landing page + waitlist Interest in the promise and the language of value 1–2 weeks
Clickable Figma prototype Clarity of the core journey 1–2 weeks, 5–8 test sessions
Concierge / manual service Whether people actually use the outcome and come back 2–4 weeks
Design sprint A fast team decision on a contested question, tested with users 5 days

The design sprint format, in which a team moves from a problem to a tested prototype in five days, was described by Google Ventures in The Design Sprint.

Common validation mistakes

  • Asking about the future. “Would you download an app like this?” almost always yields an optimistic, useless answer.
  • Talking to friends and colleagues. They want to be supportive, not to give an honest signal.
  • Presenting the solution in the first half of the interview. After a demo, people discuss your idea rather than their problem.
  • Not defining the success criterion in advance. Then any result can be read as “broadly positive.”
  • Counting likes and views instead of actions that cost people time, contact details, or money.
  • Testing everything at once. One experiment, one hypothesis.

Checklist before development starts

  1. The problem is stated in one sentence and confirmed by real instances.
  2. At least 8 interviews were held with one clearly defined group.
  3. Current alternatives and their cost to the user are known.
  4. The words the audience uses for the need are collected and used in the prototype.
  5. A minimum experiment was run against a predefined criterion.
  6. There is a written decision: what we build first and why.
  7. There is a first estimate of how the product will pay off — see our article on whether a mobile app pays off.

A strong validation does not guarantee success. It reduces uncertainty and shows which problem deserves attention first. That saves team time and makes the eventual MVP much more precise. For the wider market context, see our overview of the key mobile market numbers for 2025.

Sources: Google Design: Making YouTube Go; Rob Fitzpatrick: The Mom Test; GV: The Design Sprint.


Originally published on the Mosmox journal: How to Validate a Mobile App Idea Before Development Begins

Top comments (0)