What Should Be Included in Your First App?
How to choose the features for your first version, with a simple framework for separating must-haves from nice-to-haves.
· 5 min read
Deciding what goes into your first version is one of the most important decisions you'll make. Include too little and the product isn't useful. Include too much and you'll spend more, launch later, and learn slower.
Start with the core job
Write one sentence: "Customers use this to ___." Every feature in version one should directly support that job.
Map the simplest journey
Walk through the steps a customer takes from arriving to getting value. For a booking app: find a provider, pick a time, book, get a reminder. Each step needs to work. Anything outside that journey is a candidate to postpone.
Sort features into three groups
- Must have: without it, the core journey breaks.
- Should have: makes the product noticeably better, but customers can succeed without it.
- Later: nice ideas that can wait for real feedback.
Be honest: most features belong in the second and third groups.
Things most first versions need
- A way for people to sign up and sign in, if the product has personal data
- The core workflow, working reliably
- Basic notifications, such as confirmation emails
- A simple way for you to manage things behind the scenes
- Privacy, security, and backup basics
Things that can usually wait
- Advanced settings and customization
- Detailed analytics dashboards
- Multiple languages
- Social features and sharing
- Native apps on every platform
A free Idea Audit includes suggested MVP features and what can wait for your specific idea.