Skip to content
The first version of your product · Poland, remote

Mobile app MVP — choosing the scope of the first version

A mobile app MVP is the first usable version of a product, focused on your audience’s most important task. We help you choose its scope, design how it works and build the app in Flutter. We start by asking what the first release should allow you to test, instead of moving the whole list of ideas into it.

We agree the price and schedule individually, once the scope is defined.

Procentownik — six tool categories
Procentownik — six tool categories

When it makes sense

You want to validate the need before a bigger investment

You have a product idea, but you need to see whether your audience will complete a specific task with it. The first version should let them do that and help you answer the questions you have set.

The feature list no longer fits the budget

We separate what is essential from what can wait. Instead of lowering the quality of the whole product, we choose a smaller scope that still makes sense to the user.

You are planning a pilot in your company

The first users might be one group of employees or a single team. We agree the conditions of use, how problems will be handled and which findings will decide further development.

You do not know where to start

Together, we describe the user, their problem and the shortest complete path through the task. On that basis, you can decide whether you first need a prototype, an integration check or a working app.

What you get

The first deliverable is a scope description: who the version is for, what it will let them do and what it deliberately does not cover yet. For each feature, we add the conditions under which it works and how it will be accepted. That way, a “finished form” means agreed behaviour, including when an entry is invalid or data is missing.

Further work may include screen design, a prototype, building the app, data connections and preparing the release. We agree what is part of the engagement before it starts. You can read more about designing the flow on the app UX/UI design page.

We also describe dependencies on your side: the materials needed, access to systems, responsibility for content and the person who makes decisions. If the first version needs an external service, we first check that it can be used as planned. A screen that displays data does not by itself solve the question of where that data comes from.

We agree how feedback will be gathered after the release. This might be a conversation after a task is completed, observing a pilot or organising incoming reports. We do not add analytics or user accounts by default. If measurement is needed, we first define its purpose and the data involved.

How we plan a mobile app MVP

We agree the price and schedule individually, once the scope and the required materials are defined.

  1. We choose the question to answer

    We define the audience, the problem and the first version’s core assumption. We write down how you will know the product is worth developing, and which findings might lead you to change direction. Getting into the app store is not the goal in itself.

  2. We agree the scope and what is left out

    We order the features by their dependencies. We choose one complete task flow and mark the items for later releases. We keep a prototype separate from a product that will genuinely serve its first users.

  3. We design and build the version

    We prepare the agreed screens and features, then check that the most important path works. We present the result against the agreed scope. We discuss the technology and platform requirements in more detail on the Flutter apps page.

  4. We prepare the release and the next decisions

    We check readiness for the agreed form of distribution. We list the known limitations and the questions for the pilot. The feedback collected becomes the basis for the next scope, not an automatic list of features to add.

How we reduce the scope without weakening the foundations

We ask whether accounts, syncing, payments and an admin panel are needed for first use. One product will need them; another can start without them. We do not remove features mechanically: every decision is weighed against the task and the audience.

A smaller scope still needs correct logic, data protection and clear messages. If users cannot complete a task because of a bug, it is hard to judge the idea itself. That is why we look for savings mainly in the number of scenarios supported, not by skipping the testing of those that remain.

When a new idea comes up during the work, we assess its impact on the release. It may replace another feature, move to a later stage or require a change to the budget and schedule. That should be a conscious decision, made before the extra work becomes part of the current engagement.

Procentownik — School, fractions
Procentownik — School, fractions

An example of our work — Procentownik

Procentownik currently has 33 modules in six categories. That does not mean the first version of your app should have a similar scope. What the set of tools does show is how different tasks can share the same rules for forms, calculations and presenting results.

The app offers two themes, Calm and Bold, each for day and night, as well as screen reader descriptions. It uses data from NBP, GPW Benchmark, the Ministry of Finance, ZUS and Polish Treasury Bonds. Calculations can work offline; refreshing external data requires a connection.

These elements need to be planned separately: the range of tools, the visual variants and the integrations are different decisions. See Procentownik as it is today to look at how each tool leads from entering data to the result and its explanation.

Frequently asked questions

How is an MVP different from a prototype?

A prototype helps you walk through the planned interface, but it may use sample data and simulated responses. An MVP should let users complete the agreed task in a working product. The choice depends on whether you want to test the navigation, technical feasibility or real-world use.

Does the first version have to run on both Android and iOS?

Not always. The choice depends on your audience’s devices and how the pilot will run. You can consider starting with one platform. If you plan to add the second, we take its requirements into account in decisions that may affect later development.

Can an MVP include payments?

Yes, if purchasing is part of what you are testing. In that case, handling entitlements, restoring purchases and errors is part of the first release’s scope. We do not treat payments as an add-on that can always be bolted on at the end without consequences.

Will the app need to be rewritten after the pilot?

We do not assume so from the outset. The agreed scope should have a foundation that allows further changes. New findings can still change the requirements; in that case, we check what can be kept and what needs rebuilding. We do not promise that every future direction will be a cost-free extension.

How do you set the budget and timeline?

Once we understand the scope, dependencies and responsibilities. We state the assumptions and what is not included in the quote. The label “MVP” on its own does not mean a single price or number of weeks. See our guide: how much a mobile app costs.

What should I prepare before we talk?

Describe the person, their problem and the task the product should make easier. Add how you will reach your first users and any known constraints. A finished specification is not necessary; just note which decisions still need to be worked out together.

Other services

App UX/UI design

Check the task flow and the screen designs before development.

More →

Flutter apps

Plan the implementation and the release for your chosen platforms.

More →

How much does a mobile app cost?

Learn what goes into a quote and the materials needed to prepare one.

More →

Tell us about your project

Tell us what problem you want to solve and who would use the first version. List the features you consider essential and those that can wait. If you have not made that split yet, describe what you are unsure about — we can start from there.

Name, email and description are required. Budget is optional.

At least 20 characters.

The ranges describe your approximate budget. They are not the studio’s price list.

We will use the details you provide to handle your enquiry. Sending this form does not sign you up for launch notifications. How we process your data.

You can also email kontakt@epdigitalstudio.pl.