From app idea to first release: How to scope an MVP

Start with the situation, then the features

Describe who the app serves, what they want to do and how they do it today. “An app for coaches” is a starting point. “Let a coach tell the whole team about a change of meeting place and see who has noticed” is easier to discuss and test.

Talk to people in the intended audience. Ask them to show their current approach and describe the last time the problem occurred. Specific events reveal more than asking whether they like your idea. Note why they might prefer the solution they already use.

Choose one task a user should be able to complete

MVP stands for minimum viable product. Here, it means a focused first version that solves a real task and helps you investigate whether the solution has value. It needs a complete user journey, from opening the app to finishing that task.

In the team example, the first release could focus on messages and acknowledgements. Payments, statistics and a social feed can wait. Sort ideas into three groups and write a short reason for each priority.

• Essential for completing the main task.
• Could improve the experience in a later release.
• Needs more evidence before a decision.

Test the biggest uncertainty first

A clickable prototype may be enough to check whether people understand the flow. A small technical experiment can establish whether the app can retrieve data from an existing system. Choose the experiment around the question you need to answer.

A prototype and an app ready for use serve different purposes. Sketches can demonstrate a proposed experience without working login, storage or error handling behind the screens. Agree on what actually works so a polished demo is understood correctly.

Make the small version properly usable

Keep the feature list focused, but plan for what happens around those features. What appears before there is any content? What happens when the connection drops, information is missing or an action fails? Clear wording, accessibility and a useful next step are part of the task.

Decide what data the service needs, who will manage its content and where users can ask for help. Test on relevant devices before release. For an iPhone app, TestFlight supports beta testing and feedback from people using real devices.

Decide what you want to learn after release

Write down a few questions before the first test. Can users finish the task? Do they understand the message? Do they return when the need arises? Conversations, observation and relevant feedback can help you assess this.

Use the findings to choose the next step. That might mean fixing a difficult flow, adjusting the idea or adding another feature. A useful first release gives you both a working solution and a clearer view of what deserves further development.