Building your first version
What features should I include in the first version of my app?
Lumos · Updated
Include the features someone needs to complete one useful task from beginning to end. Choose what you want to learn from that first version, then ask which features the task depends on. Keep other ideas on a list for later.
A first version, often called an MVP, gives you something people can use and react to. Y Combinator's guidance on testing ideas recommends releasing a small first solution and learning whether it helps the people you've chosen.
Draw a boundary around the task
Imagine a designer who needs a client's decision on a draft. A first version could let the designer add a draft link and a question, let the client answer, and save the response for the designer to read.
That trial needs:
- A way to create and share the request.
- A way for the client to submit an answer.
- A saved answer the designer can find again.
- Access limited to the intended people.
File uploads, project dashboards, and automatic reminders can wait if the designer can complete this trial without them. Sending the request link manually may be enough for now.
Keep the promise of the interface honest. A button that says it saves an answer must save it. If saving fails, the person needs to know and be able to try again.
Write one completion check before building: create a request, open it as the client, respond, then find the saved response as the designer. That gives you a concrete way to decide whether this version is ready to try.
In the Builders Handbook
Read what your first version is for and use the exercise in choose one useful journey to set your scope.