What an MVP is (and what it isn't)
MVP stands for minimum viable product. For an app, it's the first version you publish with just what one type of user needs to do one specific thing, and its job is to teach you something: whether people use it, how they use it and what they miss. That tells you what to build next.
An MVP is not:
- A half-finished app. What it does, it does well: it's designed, tested and published in the stores. It has fewer features, not lower quality.
- A prototype. A design prototype is a set of screens you can click through but that don't work: it's for validating the design before coding. An MVP is a real app with real users.
- A throwaway test version. Planned well, the MVP's code is the foundation of the full app: whatever comes next is built on top of it.
When to start with an MVP, and when not to
It makes sense when there's an important question that only users can answer:
- It's a new product and you don't know whether people will use it, or which of its features really matter to them.
- You need to show something that works to convince investors, a partner or management before investing in the full app.
- Your budget is limited and you'd rather spend it on what users confirm they need.
It makes less sense when:
- The app replaces something that already exists and users expect, from day one, everything they already had. An internal app that replaces another can't launch with half the features.
- The minimum is already big. If the app is useless without connecting to your ERP or without an offline mode, that goes into the first version, and the MVP will look a lot like the full app.
- Some requirements don't come in a minimal version. In a pilot with patients or study participants, health data protection is complete from day one; we explain it in health and research apps.
What goes in and what stays out
A good MVP fits in one sentence: who uses it and what they get done. To get to that sentence:
- One main action, the one that gives the app its purpose, working well. In a loyalty app like Club RUBI, it's registering a tool and earning points; the catalogue, promotions and calculators round it out.
- One type of user. If the app will have customers, professionals and administrators, the MVP starts with the one that matters most. Every extra profile multiplies screens, permissions and testing.
- What the action needs to work, and nothing else: sign-up and login if needed, the screens for the action, and a way for your team to manage content or users.
- A backend you don't build from scratch. With Supabase, the database, sign-in and files are already handled, and they're configured rather than coded. If the app later needs its own logic, it's added on top.
What usually stays out of the first version:
- Integrations with corporate systems (ERP, CRM, corporate login), unless the app is useless without them. At first, loading the data from the dashboard or from an exported file is often enough.
- A tablet version, if people will mostly use it on their phones.
- Several languages, if your first users share one.
- Offline mode, unless it's used where there's no signal.
- Just-in-case features: settings, statistics or customisations nobody has asked for yet.
And what doesn't get cut: security, data protection, what Apple and Google require to publish it, and a way to measure how it's used. Without data, an MVP teaches you nothing.
How to cut the scope
Write down every feature you can think of, without filtering, and then run each one through three questions:
- Does the main action work without it? If so, it can wait.
- Can it be done by hand at first? Approving sign-ups, sending a notice or loading the catalogue can be done by your team from the dashboard while there are few users. When it starts taking real time, it gets automated.
- What will you learn from it? If a feature doesn't answer any question about the idea, it belongs in the second version.
You end up with two lists: the must-haves, which are the MVP, and the nice-to-haves, ordered by what you think they'll bring. The second list isn't lost: it's the plan for the next versions, reordered by what users actually do.
A prototype of the key screens helps you cut: showing it to a few users before coding reveals features you don't need and one or two that are missing, when changing them takes minutes rather than days.
Native, cross-platform or web for an MVP
There are three ways to build an MVP:
- A web app (PWA). It opens in the browser and doesn't go through the stores. It's the fastest to publish if the idea doesn't rely much on the phone, but it has limits: it isn't in the App Store or Google Play, and on iPhone notifications only arrive if the user adds it to their home screen.
- A native app for iOS and another for Android. Two codebases: twice the work for every change, just when an MVP changes the most.
- Cross-platform with React Native, which is what we use: a single codebase for iOS and Android with native performance and look, and native code when a part needs it. For an MVP there's one more advantage: every change users ask for is made once and reaches both platforms.
If you're unsure whether to start with one platform or both: with React Native, building both costs a bit more than building one, nowhere near double, and you don't leave out the people on the other one.
What it costs and how long it takes
An MVP costs less than the full app because it does less, not because it's built differently. The ranges are the ones in our cost guide, and a well-scoped MVP usually falls into the first:
- Just the essentials: €10,000 to €20,000, 2 to 3 months. A few screens, users who sign up and log in, and a backend on Supabase, configured rather than coded.
- With a custom backend: €20,000 to €50,000, 3 to 5 months. When the main action needs its own logic, such as points and rewards or notifications based on what each user does.
- From €50,000, 5 months or more, if the must-haves already include connecting to corporate systems or demanding requirements, such as offline mode. Then it's worth asking whether the MVP can start without them.
Prices exclude VAT and include design, development for iOS and Android, and publishing in the stores. Servers, maintenance and the Apple and Google developer accounts are separate.
A timeline tip: start setting up the Apple and Google accounts at the beginning of the project. Between the D-U-N-S number and the reviews, a couple of weeks can go by, and in an MVP that time counts. Our cost guide explains how to do it.
What happens after launch
An MVP starts paying off once it's published:
- Measure. Before launch, decide what will tell you the idea works: how many users complete the main action, how many come back the following week. And make sure the app measures it from day one.
- Talk to users. Data tells you what they do; conversations tell you why.
- Iterate. With what you've learned, you reorder the nice-to-haves and quote the next version as a small project.
- Keep the app up to date. Apple and Google release new versions of iOS and Android every year and require apps to be updated, MVPs included. Our basic maintenance, from €99 a month excluding VAT, keeps it up to date in the stores.
And if the data says the idea doesn't work as you expected, that's a result too: you found out with part of the budget, not all of it.
How to get a quote for an MVP
We start with a 30-minute call to understand what you want to test, who the app is for and what constraints there are. Then we send you a proposal with scope, timeline and budget. On small projects, which an MVP usually is, the price is fixed for the whole project, and from the start you have test versions on your phone to see how the app is coming along.
If you're comparing companies, our guide on choosing an app development company explains what to look for in each quote.