Category
Knowledge base
Subject
App development
Reading time
14 minutes
Level
Decision maker
Updated
May 2026

How much does it cost to build an app?

An honest explanation of what building an app costs in 2026 — and above all: which levers you control to push those costs up or down. For founders, product managers and executives who want to know enough to have a good conversation with their development partner.

What determines the cost of building an app?

The question "what does an app cost?" is about as concrete as "what does a house cost?". A tiny house in a field is a different thing from a listed canal house, and the same goes for apps. An internal tool for twenty employees is a different beast from a consumer app that has to handle peak load in the second week after launch. What we can do is map out the levers that determine the cost of an app: technology choice, scope, features, design, ongoing maintenance and how much you contribute to the design yourself.

In our experience, the following factors carry the most weight:

  • Technology choice: native, cross-platform, web app or hybrid: each model has its own cost profile.
  • Scope: how many screens, how many roles and how many use cases the first release needs to cover.
  • Custom design vs. component library: the more pixel-perfect and different from standard patterns the design is, the more design and build time it takes.
  • Backend and data: just a shell on top of existing APIs, or does new backend logic and database modelling need to be built as well?
  • Integrations: how many external systems need to talk to the app, such as accounting, CRM, payments, push notifications, identity and analytics.
  • Compliance and security: does the app process personal data, payments, medical data or enterprise-level login credentials?
  • Maintenance: who keeps it running once version 1 is in the stores?

We work with fixed sprint budgets and agree a scope per sprint in advance, so you can adjust course at any time. We'd be happy to discuss a detailed breakdown for your specific case in an introductory meeting. For a broader picture of what software development typically costs, you can also read our page on custom software costs, as many of the principles overlap with app budgets.

i
Key point

The price of an app is determined by your choices, not by a price list. We help you sharpen those choices before a single line of code is written.

Native or cross-platform: the biggest cost lever

The first serious decision is almost always the technology choice. Broadly, there are three flavours: native, cross-platform and mobile web. Each has its home turf.

Native (Swift / Kotlin)

For iOS you build in Swift, for Android in Kotlin. Two codebases, two disciplines, two teams or double the expertise. Native gives you the best possible performance, full access to platform features and the most refined user experience. The trade-off is that you are effectively building twice. For apps with heavy graphics, camera or sensor use, native remains the first choice.

Cross-platform (Flutter, React Native)

One codebase that delivers both iOS and Android. Flutter (from Google) and React Native (from Meta) are both mature, fully fledged frameworks that in 2026 can handle pretty much anything a native app can. For most B2B apps, MVPs and consumer apps without a heavy graphics workload, this is the pragmatic choice: a single codebase that cuts the overall build effort by roughly a third to a half.

Mobile web / progressive web app

A web app that works on a phone, with no store installation needed. It's cheaper and faster to launch, but it has no access to push notifications on iOS (Apple restricts these heavily), no rich offline mode, and users won't find it through the app stores. A fine choice for internal tools or B2B portals; rarely the winning route for consumer apps. Also read our guide on build vs buy if you're unsure whether you should build anything yourself in the first place.

ApproachStrong inCost profile
Native iOS + AndroidPerformance, sensor access, premium feelHighest: effectively two builds
Flutter / React NativeOne codebase, fast iteration, B2B appsMedium: one codebase, two outputs
Progressive web appNo store, quick rollout, internal useLowest, but with functional ceilings

iOS, Android or both?

We get this question more often than you might think: does the first version really need to be on both platforms? The answer depends on your target audience, not on your preference.

For consumers in the Netherlands, the market share is roughly fifty-fifty between Android and iOS — launching a consumer app on only one platform means missing half your market. Among business users in the Netherlands, iOS is over-represented, especially in management, sales and marketing roles. For logistics, warehousing and field service, Android dominates because the hardware is cheaper and more robust.

A legitimate strategy is to start cross-platform and serve both stores at once — which is exactly why Flutter and React Native have become so popular for MVPs. If you want to go native but keep the budget under control, you can launch one platform first and use early user insights to decide whether the second platform is worth it. For app development we offer both routes — we advise based on your target audience, not on what is technically the most fun to build.

App types: not every app is the same

"Building an app" is an umbrella term. Under that umbrella fall very different projects with very different price tags. A handful of scenarios we see regularly:

Consumer app (B2C)

Aimed at the general public, available in both app stores, with onboarding, accounts, push notifications, in-app payments and strict demands on polish and performance. This is the most expensive category because everything has to be right: design, copy, edge cases, App Store reviews, support for older devices. An MVP is a serious risk here — a mediocre consumer app immediately attracts low reviews and is hard to rescue.

B2B app for customers or partners

An app for your existing customers or suppliers. Known users, often linked to your existing backend, and less dependent on viral onboarding tricks. The business case is usually clear: efficiency, retention, or an extra service layer on top of an existing product. Cross-platform is almost always the right choice.

Internal app for your own employees

For example, a field service app for technicians, an order-picking app for the warehouse or a reporting tool for managers. The user group is known and trained, you can specify the hardware yourself, and the design requirements are lower. This is almost always the most cost-efficient category. A progressive web app is often good enough here.

MVP / pilot

A deliberately stripped-down first version to test a hypothesis. Not the same as "a cheap app" — an MVP is a learning tool, not a production system. The value lies in what you learn in the first few months, not in what you deliver in week one. This is where we see the most waste: teams that build an MVP as if it were a production app, or teams that build a production app under the banner of an MVP.

Production app

The mature version. Robust, monitored, tested, scalable, with a release pipeline. It is no coincidence that the step from MVP to production app is often more expensive than the MVP itself — everything you took for granted in the MVP now has to be properly structured.

Which features drive up the budget?

Not every feature costs the same. A handful of categories that have the biggest impact on the budget in practice:

  • Real-time functionality: chat, live updates, multi-user editing. Requires websockets or dedicated infrastructure and considerably more backend work.
  • Offline mode: apps that must also work without a connection and sync later. Data consistency suddenly becomes a headache — expect significantly more testing.
  • Custom UI vs. component library: if every screen is uniquely designed and not built from a design system, build time increases quickly. A good component library is your best budget ally.
  • In-app payments: Apple and Google take a 15-30% commission on digital goods in their stores. On top of that, you have to implement Apple's In-App Purchase API or Google Play Billing, with restores, refunds and family sharing edge cases.
  • Push notifications: basic push is cheap, but targeted segmentation with rich content and deep linking is a sub-project of its own.
  • Camera, scanner, sensors: scanning QR codes costs almost nothing, but product photos with machine learning classification is a serious undertaking.
  • Integrations: every external API you connect costs design, build, error handling and monitoring. Read what an API integration actually involves if you want to dig deeper.
  • Authentication: simple email and password is cheap. Single sign-on with Microsoft, Google, Apple or an enterprise IdP is a substantial extension.
  • Location and maps: standard maps are affordable; routing, geofencing and maps with many custom layers quickly get expensive, both in build costs and in monthly map tile fees.
  • Backend APIs: if the app is a shell over an existing system that already has a good API, you save a lot of work. If new backend logic has to be built, that is a whole separate project.

A useful rule of thumb: cut every feature you are not certain has to be in version one. Version two is a better place for the borderline cases, as long as you keep them within reach.

Hidden costs people run into

The build costs are often only half of the total picture. What you keep spending on an app after launch is routinely underestimated. The main items:

App store accounts

An Apple Developer account costs a fixed amount every year. For Google Play Developer you pay a one-off registration fee. It sounds small, but nothing happens without those accounts, and with Apple the renewal process has gone wrong more than once.

App Store review process

Every release has to pass Apple's review team. It is usually done within a few days, but sometimes it is rejected on the basis of Apple's Human Interface Guidelines or rules around payments. That is not a cost item in euros, but it is in lead time, and when your release fixes something that is broken in live production, every day of waiting feels very long.

Releases per year

An app that is "finished" does not exist. Every release costs design, build, testing and the whole review process all over again. Expect a few larger releases per year plus individual fixes. Apps that never get an update eventually drop out of the market, and users can see that from the release history.

OS updates and device fragmentation

Apple releases a new iOS every autumn; Android follows its own pace. Sometimes such an update breaks something in your app. Maintaining compatibility with the latest two iOS and Android versions is part of ongoing maintenance. On Android, there is also the variety of devices, screen sizes and manufacturer-specific ROM modifications on top.

Security updates and library maintenance

Mobile apps use dozens of open-source libraries. Somewhere among them there is a security patch almost every month. If you do not keep up with them, after a few years you end up with an app that only someone with a great deal of patience can update.

Backend hosting and SaaS licences

The backend has to run somewhere, and cloud hosting costs money every month. Push providers, error tracking (Sentry or Bugsnag), analytics (Mixpanel or Amplitude), authentication (Auth0 or Cognito), maps (Mapbox or Google), email (Postmark or SendGrid): each of these services is affordable on its own, but it adds up.

App Store and Play Store commission

If you sell in-app purchases, 15-30% goes to Apple or Google. For SaaS businesses, that is a serious item to factor into your pricing model.

!
Tip

With every proposal, ask not only about the build costs, but also about the expected maintenance and the annual third-party licence costs. Apps that turn out more expensive in year two than they seemed in year one are a classic pitfall.

MVP versus production app: the real trade-off

Many teams struggle with the choice between "getting something to market quickly" and "getting it right from the start". Both positions have their merits, but the choice has an enormous impact on the budget and on the success of the project.

A good MVP is a product with just enough functionality to validate your core hypothesis. It is not a demo, not a clickable prototype, but not a production app either. The value of an MVP lies in what you learn: will real users actually do what they said they would? Is the pricing model right? Where do people drop off? You can only answer questions like these with software that people can actually use.

A production app has a different purpose: working at scale, for a long time, in a market you already understand. Here, things like observability, automated tests, error handling, release processes and compliance need to be right from day one. Building a production app at the scale of an MVP is more expensive and delivers less than doing the two as separate projects.

The dangerous middle ground: a team that promises an MVP but in practice builds a production app without the accompanying quality layer. That is the worst of both worlds, more expensive than a real MVP and more fragile than a real production app. In the first session, we explicitly discuss which of the two you need, and steer accordingly.

What determines a mobile developer's hourly rate?

An hourly rate doesn't tell you much until you know what you get for it. Three factors play the biggest role:

  • Seniority and experience: a senior iOS engineer with hundreds of apps in the stores delivers more in less time than a junior who still has to climb the learning curve. The hourly rate differs considerably, but the total budget often differs less than you might think, because seniors produce less rework.
  • Specialism: regular app builders are scarcer than web developers and therefore more expensive. Whole niches (AR/VR, complex Bluetooth/BLE, low-level audio processing) have their own rate levels again.
  • Location and model: Dutch agencies charge higher rates than offshore teams. The question is what you get in return in terms of communication, time zone, legal footing and quality, and that trade-off differs for every project.

We are a Dutch development partner with a permanent team, and we work with sprint budgets. There is a transparent hourly rate underneath, but you steer on sprint output: at the end of each sprint you receive working functionality, not a timesheet. For larger or business-critical projects, you can also take a look at our page on custom enterprise software development.

And what about no-code platforms such as FlutterFlow and Glide?

An honest take: no-code and low-code mobile platforms such as FlutterFlow, Glide, Bubble (web) and Adalo have matured considerably in recent years. They are a legitimate choice in a number of scenarios, but absolutely not for everything.

Where no-code works well: proofs of concept, internal tools for a handful of users, standardised flows (forms, dashboards, simple CRUD apps), or validating an idea before you commit a development budget. We have seen clients get a first internal tool up and running in a few weeks with FlutterFlow that would otherwise have taken months.

Where no-code breaks down: when the app becomes a structural part of your business, as complexity grows, with strict compliance requirements, with large numbers of users, when you need a rich offline mode, or with integrations that fall outside the platform's standard offering. Vendor lock-in is a serious issue: you can hardly migrate to your own codebase without pain.

Our sober take: use no-code for what it is, a fast, affordable way to get something to market and learn from it. But agree up front that if the app takes off and becomes serious, you will lay a new foundation with proper software. That is not failure, that is a normal life cycle.

Frequently asked questions about the cost of an app

Which is cheaper: native or cross-platform?

In almost every scenario, cross-platform is cheaper if you want to serve both platforms — you maintain one codebase instead of two. Native only wins on cost if you target a single platform exclusively, or if your app depends heavily on platform-specific features that Flutter or React Native can't handle well enough.

Should I start with an MVP or build a production app straight away?

That depends on how confident you are in your hypothesis. If you don't yet know whether people will use it, build an MVP and accept that it will be limited and rough. If you already have evidence that the need exists — for example because you're already seeing ad-hoc workarounds — you can consider going straight to a slimmed-down production app. The dangerous middle ground is building an "MVP" as if it were production.

How long does it take to build an app?

For a simple cross-platform app we're talking a few sprints; a production consumer app takes several sprints. But the timeline depends less on the technology than on how sharply defined your scope is and how quickly you can make decisions along the way. In our experience, projects overrun because of decision-making more often than because of the build work.

What do I need to know about the App Store and Google Play?

You need an Apple Developer Account and a Google Play Developer Account — you open these in your own company's name, not your agency's. We guide the first release, including writing the store listings, creating screenshots and handling the review process, but you remain the legal owner of the apps in the stores. This matters for exit scenarios.

Can we keep releasing updates after the app is live?

Yes, and we recommend it. Apps that sit untouched for months rank poorly in the stores and lose users. We work in continuous sprint cycles in which we add functionality, apply security updates and keep the app compatible with new iOS and Android versions. You can also take this on in-house once your team understands the codebase — we document everything and are happy to run handover sessions.

Can we start with a no-code platform and switch later?

Technically it's possible, but don't underestimate the migration. No-code apps have their own data models, their own flows and their own place where the business logic lives. A full rebuild is almost always needed — what you carry over is mainly the validated requirements, not the code. That's not a problem in itself, as long as you build that moment into your planning from the start.

The three key points.

01

Your choices determine the price

Technology, scope, design complexity, integrations and maintenance — not a price list. If you know which levers to pull, you help steer the budget.

02

Cross-platform is usually the pragmatic winner

Flutter and React Native cover most B2B, MVP and internal apps perfectly well. Native makes sense for premium consumer apps and heavy sensor or performance requirements.

03

Maintenance isn't optional

App store accounts, releases, OS updates, security patches and SaaS licences belong in your budget from day one. Apps that aren't maintained lose users.

Talk to us about the cost of your app?

An introductory call of half an hour. We listen to what you want to build, for whom and why — and immediately give you an honest estimate of scope, complexity and the levers you can use to steer the budget yourself.

Edit content