What Should Your App MVP Actually Include?
A framework for knowing what to include in app MVP scope — by ruthlessly cutting to the one feature that proves users return after day 7.
Most founders we talk to arrive with a list. A long one. Onboarding flow, social sharing, in-app chat, push notifications, dark mode, referral codes, admin dashboard, five filter options — all marked “MVP.” By the time we ask what the app is actually for, we’re already ten features deep into a product that will cost $80k and take nine months to ship.
Understanding what to include in app MVP is not about trimming your list by 20%. It is about asking one question that changes how you think about scope entirely: will a user come back on day 7?
If you can answer that question with a working app, you have an MVP. If you cannot, you have a feature set in search of a product.
Why Day 7 Is the Right Test
Retention is the only metric that tells you whether your product has a reason to exist. Not downloads, not sign-ups, not App Store ratings — retention.
Day 7 return rate matters because:
- Day 1 can be curiosity or a friend’s recommendation. It proves nothing.
- Day 3 shows the app didn’t crash and was at least interesting enough to revisit.
- Day 7 shows a user found enough value to build a habit. That is what investors, revenue, and word-of-mouth are built on.
Your MVP’s job is not to impress people. It is to answer the question: does our core value proposition actually change user behavior in a lasting way?
Every feature you add beyond what answers that question is a hypothesis that can wait.
The One-Feature Framework
Before writing a single line of code — or paying a studio like us to write it — you need to identify your core retention driver: the single action a user takes in your app that correlates with coming back.
For a space launch tracker like Launchcast, that action is setting a launch alert. If a user sets one, they come back when it fires. Everything else — maps, crew bios, mission history — is valuable context, but none of it drives the return.
For a cooking assistant like Clove AI, that action is completing a recipe plan. If a user builds and executes a meal plan once, they come back to plan the next week.
To find your core retention driver, ask:
- What is the one thing a user does in this app that makes their life measurably better?
- How quickly can they do it — in their first session?
- Is there a natural reason to repeat that action?
If your answers are sharp and specific, you have a retention driver. If they are vague (“browse content,” “explore features”), you have a branding exercise, not a product.
What Belongs in Scope — and What Doesn’t
Once you have your core retention driver, use it as a filter. Every feature either supports that driver or it doesn’t.
MVP Scope: Include
| Feature | Why It’s In |
|---|---|
| The core user flow, end-to-end | This is the product. Without it, nothing else matters. |
| Authentication (sign up / log in) | Required for personalization and data persistence. |
| Basic push or email notifications | If your retention driver has a time component, the user needs a nudge. |
| Crash reporting and basic analytics | You need signal on what is breaking and whether the core flow is completing. |
| App Store compliance package | Icons, screenshots, privacy policy — required to ship at all. |
MVP Scope: Cut
| Feature | Why It’s Out |
|---|---|
| Social sharing / referral system | Valuable for growth, irrelevant to proving retention. Build it in v1.1. |
| Admin dashboard | Founders can use direct database access or simple tools. This is internal tooling. |
| Multiple onboarding paths | One clear path. Optimize once you have data on where users drop off. |
| Advanced settings and customization | Users who return day 7 on a bare-bones product are your real base. |
| Offline mode | Important eventually, but adds significant complexity. Validate demand first. |
| Dark mode and accessibility polish | Valuable, but not a retention driver. Ship it in the next update. |
The pattern: if a feature is about discovery or delight, it can wait. If it is about completing the core value exchange, it stays.
How Scope Directly Affects Your Budget
This is where the business case gets concrete. At Fera Tech, we scope projects into three tiers based on complexity — and the difference between them is almost always the number of features, not the quality of the core product.
- Simple MVP ($5–15k, 2–4 months): One core flow, standard auth, basic analytics. No real-time data, no AI, no complex integrations. A booking app, a simple tracker, a directory — well-scoped, this is entirely achievable.
- Standard app ($15–45k, 4–7 months): Several interconnected flows, a backend with business logic, third-party integrations (payments, maps, calendars), more complex UX. This is where most products should start if the core retention driver requires live data or user-to-user interaction.
- Complex app with AI or real-time features ($45–120k+, 7–12 months): On-device ML, generative AI features, real-time sync, multi-platform. This scope is justified only when the core retention driver requires this complexity — not when it would be “cool to have.”
When a founder shows us their feature list and the quote comes back at $80k, our first question is: which three items on this list are the ones that bring users back on day 7? The answer is almost always two or three features. The rest is scope that can be phased.
See examples of products we’ve scoped and built at /#work, or learn about our development services at /#services.
A Practical Scope-Cutting Checklist
Before finalizing what your MVP includes, run every proposed feature through this checklist:
- Does removing this feature break the core retention driver? If no, cut it.
- Can a workaround (manual process, external tool, founder doing it by hand) cover this for the first 100 users? If yes, cut it.
- Does this feature require data or user behavior we don’t have yet? If yes, cut it — you cannot personalize what you haven’t measured.
- Is this feature about acquiring users or retaining them? If acquisition, cut it from MVP. Retention comes first.
- Would a user notice if this feature launched two months after the core app? If no, cut it from v1.
Running a 15-feature list through this checklist reliably produces a 4–6 feature MVP. That is not a limitation — it is the product you can afford to build well, ship fast, and iterate on with real data.
Common Questions
Q: Won’t a minimal MVP look unprofessional to users?
A well-scoped MVP is not a half-finished product — it is a focused one. Users forgive missing features far more readily than they forgive crashes, slow load times, or a confusing core flow. A tight, fast, reliable app with one great feature beats a sprawling app with ten mediocre ones every time. Quality in the core flow is non-negotiable; breadth of features is not.
Q: What if my investors expect a more complete product before funding?
Investors who back early-stage products are evaluating traction and signal, not feature completeness. A day-7 retention rate of 30–40% on 200 real users is a stronger investment case than a polished demo with zero real usage data. Build the thing that generates the signal, not the thing that looks impressive in a slide deck.
Q: How do I know if my core retention driver is the right one?
Talk to 10–15 people who have the problem you’re solving before you build anything. Ask them what they do today to solve it, how often they do it, and what they would pay to solve it better. If the answers cluster around a specific behavior or pain point, that is your retention driver. If the answers are scattered, you need more customer discovery before you scope an MVP.
Ready to Scope Your MVP?
If you have a product idea and want a realistic picture of what it should include, what it will cost, and how long it will take, we are happy to have that conversation. We have built and shipped 12+ apps across iOS, cross-platform, and AI-integrated stacks — from consumer products like Launchcast and Clove AI to client work spanning the US, Europe, and Central Asia.
The scope conversation is free. Most founders leave it with a much clearer product and a much shorter feature list.
Get in touch at /#contact and tell us what you are building.
Building something like this?
Fera Tech ships iOS & full-stack apps end-to-end. Tell us about your project.
Start a project