Flutter apps
Building the app and preparing the release for your chosen platforms.
More →How much does a mobile app cost? The answer depends on what users need to do in it, where the data comes from and what the engagement covers. At EP Digital Studio, we break down design, development, integrations, testing and release preparation, so that the price relates to a specific scope.
We agree the price and schedule individually, once the scope is defined.

We price the agreed scope. A description such as “an app for Android and iOS” or a number of screens is not enough, because a similar interface can handle simple local data or a complex company system. The initial conversation is about working out what needs to be clarified before we can give a figure.
The first factor is the app’s tasks and states. A form needs more than fields: it needs data validation, messages and a plan for when the server does not respond. With different user roles come permissions: who can see information, who can change it and what happens when access is revoked.
The second factor is data. Calculations done on the device have different requirements from a shared database with accounts and syncing. If information has to be available offline and edited on several devices, you need to decide how conflicts are resolved. The phrase “works without the internet” does not describe that behaviour on its own.
Integrations with external systems depend on the available connections, documentation and testing conditions. Responsibility for the server and the admin panel is agreed separately. We include payments, notifications and phone features when the product’s use case calls for them, together with their handling and testing.
The scope also depends on how complete the materials are: screen designs, content, calculation rules and access. Existing wireframes can help, but you need to check that they cover every situation required. You can read more about this part of the work in our description of app UX/UI design.
The options below show approximate budgets and timelines for an example set of features. The final quote and schedule are agreed individually.
| Option | Example feature set | Approximate budget (net) | Approximate timeline |
|---|---|---|---|
| Local tool | forms, calculations, on-device storage, no accounts | from PLN 20,000 (approx. EUR 4,600) | from 5 weeks |
| App with accounts and server-side data | sign-in, syncing, admin panel | from PLN 46,000 (approx. EUR 10,500) | from 2 months |
| Product with integrations and purchases | payments, external services, several user roles | from PLN 92,000 (approx. EUR 21,000) | from 4 months |
All amounts are net of VAT (23% VAT is added where applicable) and cover a single Flutter codebase for Android and iOS. Euro amounts are approximate. The timeline runs from scope approval to a release-ready build and does not include app store review.
Compare offers together with their assumptions. Check whether the price includes design, the server, testing, store materials, documentation and fixes after acceptance. The list of exclusions matters as much as the list of features; it helps establish what the client needs to provide.
Each option is priced individually. We agree the schedule once the features, dependencies and responsibilities are clear.
We agree what preparing the offer involves when you get in touch. If a separate discovery phase is needed, we first agree what it will deliver and on what terms.
A shared codebase lets Android and iOS share part of the logic and the interface. It does not remove each platform’s own requirements, testing and release preparation. That is why we do not promise a single percentage saving for every project. We describe what the technology is used for on the Flutter apps page.
Choose one complete user scenario and note the others as later stages. Check whether all the roles, integrations and payment options are needed from the start. Fewer features help keep the scope under control, as long as users can still complete the task that matters.
Do not postpone correct logic, data protection and testing of the most important functionality. We reduce the product’s scope; we do not pretend that testing disappears. We describe how we approach a first version on our mobile app MVP page.
Maintenance and new features are separate scopes. You need to account for operating system and dependency updates, changes to integrations and handling support requests. If the product uses a server or paid services, their fees are a further item that depends on the specific configuration and usage.
Developer accounts and external services are billed on their providers’ terms. We do not include them in the studio’s fee by default. Responsibility for accounts, costs and access should be set out in the offer. We do not give unverified figures here, or a one-size-fits-all maintenance rate.

Procentownik includes 33 modules in six categories, two themes for day and night, and screen reader descriptions. Calculations can work offline; updating data from NBP, GPW Benchmark, the Ministry of Finance, ZUS and Polish Treasury Bonds requires a connection.
In a product like this, calculation rules, the interface, data storage and data freshness are separate areas of work. The number of modules is not a ready-made price multiplier. See our product to compare a simple converter with a tool that needs a complex form and a visual explanation. These are the differences worth considering when you describe the scope.
Quotes for a simple local tool start at PLN 20,000 net (approx. EUR 4,600), with an approximate timeline of 5 weeks or more. That scope covers forms, calculations and on-device storage, without user accounts. The final quote and schedule are agreed individually.
It is enough to start the conversation. How precise the offer can be depends on understanding the features, the data and the responsibilities. If key information is missing, we first list the questions that need answering, rather than giving a figure without explaining its assumptions.
It helps us suggest a realistic first scope. It is not an automatic agreement to spend the whole amount. The ranges in the form describe your budget; they are not a price list or a commitment from the studio.
Not directly. One screen can handle complex logic and an integration, while several others can reuse existing components. We assess how the app works, its variants and its testing, not just the number of views.
It depends on the agreed scope. The offer should state whether the design is provided by the client or prepared by the studio. In the same way, we separate development, the back end, content, release preparation and further development.
Preparing the release can be part of the engagement, but store decisions are not up to the studio. The scope should state who is responsible for materials and for responding to review feedback, without guaranteeing acceptance or a release date.
We describe the change and its impact on existing functionality, testing and the release. We then agree a separate scope or update the roadmap. We do not assume that every new feature fits within the earlier price.
Describe the user, the most important feature and the data the app should use. Add any materials you already have and an approximate budget. Let us know what has already been decided and where you need help making a decision.