This article was originally published in the Indie App Devs newsletter and written by Damjan Dabo.
When you’re building a new app, the temptation to make it “perfect” before launch is strong.
But perfection is a trap.
The real goal of a minimal viable product (MVP) is to ship your app as quickly as possible, validate your idea, and start learning from real users.
The sooner you put something in people’s hands, the sooner you can see if your app solves a real problem, and adjust your direction based on feedback rather than guesswork.
What to Include in Your MVP
1. Your Main Feature (and Nothing Else)
Your MVP should focus entirely on the core benefit your app delivers.
Ask yourself: What is the single most important problem my app solves?
Then, build only the features required to solve that problem well. “Minimal” doesn’t mean “half-baked.” Your main feature should work reliably, handle all error and loading states gracefully, and account for edge cases.
A lean app is good. A buggy one is not.
2. Clean, Simple UX/UI Design
First impressions matter for usability as much as they do for visuals. Even with an MVP, aim for a design that feels clear, uncluttered, and easy to navigate. Stick to native UI components, a consistent color palette, and predictable patterns so users can focus on what your app does, not how to operate it.
Good design isn’t about adding complexity, it’s about removing friction.
3. Stability and Error Handling
No matter how minimal your app is, it should feel stable. Crashes, unhandled errors, or stuck loading states will destroy user trust fast.
At MVP stage, prioritize: A crash-free launch rate close to 100%
Clear error messages when something goes wrong. Fallback states for slow or failed network calls.
You don’t need a perfect app, but you do need one that works reliably.
4. Onboarding That Sells the Value
Even in an MVP, onboarding should clearly communicate the benefits and value of your app.
Think of it as the warm-up act before the paywall. It sets the tone and explains why someone should care.
For an MVP, a simple three-screen onboarding flow is often enough. You can always personalize or expand it later.
5. A Paywall (Placed Right After Onboarding)
Most in-app purchases happen during onboarding, so include a paywall early in the experience.
Tools like RevenueCat Paywalls or Superwall can help you start A/B testing prices and offers from day one.
6. Analytics From Day One
Without analytics, you’re flying blind. You need to know how people use your app to make informed decisions.
Start tracking essential metrics from launch, such as:
- First open
- Onboarding completed
- Paywall shown
- Paywall purchased
- Main feature used
This early data will guide improvements and help you prioritize features.
7. A Feature Request System
A built-in way for users to suggest and vote on features not only gives you valuable feedback but also increases retention. When people have a say in what comes next, they feel more invested.
If possible, let users subscribe to updates on the features they’ve voted for (“Email me when this is live”). This creates a built-in reason to bring them back to your app later. On iOS, WishKit is a great option for adding features wishlist to your app quickly.
8. A Way for Users to Contact You
Early feedback is gold, and sometimes users won’t submit feature requests but will still have questions, bug reports, or suggestions. Make it easy for them to reach you directly.
This could be as simple as:
- An in-app “Contact Us” button linking to email or a form.
- A help/support section with a feedback form.
- A public email address in the settings screen.
The easier it is for users to talk to you, the faster you can fix issues and improve your app.
What Your MVP Doesn’t Need
1. “Nice-to-Have” Features
Small quality-of-life improvements and polish can make your app feel premium, but they aren’t necessary to prove your idea works. Leave these for later once you have traction.
2. Multiple Platforms
If you’re a native iOS or Android developer, resist the urge to launch on multiple platforms at once. Focus on one, validate your idea, and only then expand. For cross-platform developers, this may be less of an issue since you’re building for multiple platforms by default.
3. Perfect Accessibility
At the MVP stage, it’s okay to ship with basic accessibility instead of a fully optimized experience. Speed matters when you don’t yet know if people want your app. But this isn’t a free pass to ignore it forever. Commit to making significant accessibility improvements in your first major post-MVP update.
In Short
Your MVP should be lean, focused, and functional. Ship fast, listen to feedback, and iterate.
The sooner you learn from your users, the sooner you can turn your idea into something people truly love.
Want to learn more?
Damjan Dabo is an indie iOS developer building and growing his own apps while sharing the journey, including wins, lessons, and experiments, in public.
Read his blog at dabo.dev for in-depth posts, and explore all his apps at bento.me/dabo.
Follow him on X/Twitter and LinkedIn for more behind-the-scenes insights.
