I have an app idea. Where do I start?

Start with a person and a problem

Describe one specific person who would use your app and the problem they currently face. “An app for everyone” gives a development team little guidance. “An app that lets local service customers book and track a technician” gives you a journey to investigate.

Speak to potential users before committing to a large feature list. Find out how they solve the problem today, what frustrates them and what would make them change their behaviour.

Describe the complete first journey

Write the steps from opening the app to receiving the result. Include what happens behind the scenes: who confirms a booking, updates an order or handles a failed payment?

A simple sketch is useful. You do not need polished designs or technical terminology to begin. An example from another app can explain a pattern, but your own business rules still need to be defined.

• Who signs in, and what information do they provide?
• What is the most important action they complete?
• What does your team need to manage that action?
• What can go wrong, and who resolves it?

Choose what to learn before what to build

A clickable prototype can help test whether people understand the journey. A working MVP can test whether they actually use it. These are different investments and answer different questions.

Choose a success signal that matters to your idea: completed bookings, repeat use, a confirmed purchase or reduced processing time. A launch date by itself is not evidence that the product is useful.

Prepare for a development conversation

Bring your audience, problem, essential journey, reference examples and any constraints on budget or timing. Mention existing tools or data that the app must connect to.

Ask the team to explain the proposed first release, assumptions, responsibilities and delivery stages in plain language. Agree how you will review working software and how changes to the scope will be handled.