App development cost in 2026: how much does it cost to build an app?

App development cost in 2026 ranges from a few thousand euros for a chatbot or a messenger mini app to six figures for a multi-role platform. For most small and mid-sized businesses, the honest answer to "how much does it cost to build an app" sits in the lower part of that range — as long as the first version does one job well instead of ten jobs badly.

Three agencies can quote three wildly different numbers for the same brief. That is rarely because someone is hiding something. It is because "an app" can mean a loyalty card with push notifications or a logistics platform with real-time tracking and four user roles. Below: what drives the price, the ranges we see in quotes across Western Europe, the running costs that are left out of most quotes, and how to get an estimate you can actually compare.

At Pazl, a focused business app or MVP for iOS and Android starts from €4,750 at a fixed price, with senior review and a six-month warranty.

What drives app development cost

Every estimate is built from the same handful of variables. Once you know them, you can read any quote.

1. Platforms: iOS, Android or both

Most business apps need both stores. A cross-platform build in Flutter or React Native shares most of the code between iOS and Android, so you pay for one codebase instead of two. Native Swift and Kotlin make sense for complex animation, heavy media or specific device functions, and cost more because two apps are built. We compare the options in cross-platform vs native development.

2. Screens and user journeys

The number of distinct screens and flows matters more than the number of ideas. An app where customers sign in, collect points and see offers is one journey. Add ordering, booking and a staff app, and you have three products.

3. Backend, integrations and the admin panel

The part users see is often the smaller half of the bill. Behind it sit accounts, a database, push notifications and an admin panel your team uses to change content, prices and offers. Each integration — a POS, a payment provider, a CRM, a booking calendar — is its own piece of work, and its price depends on how good that system's API is. A loyalty app that talks to your till is a different project from a brochure app with a contact form.

4. Design

An app built on a proven set of components costs less than one where every screen, icon and animation is drawn from scratch. Custom design pays off when the app is your main sales channel; for an internal tool it rarely does.

5. User roles and permissions

A customer app has one role. A marketplace has at least three: buyers, sellers and admins. Every role means its own screens, rules and tests.

6. Who builds it

Freelancers, offshore teams, nearshore studios and local agencies price differently. The difference is not only quality: it is also who answers when something breaks six months after launch, who owns the code and whether there is a second person who knows the project.

App development cost ranges in 2026

The ranges below are, by our estimates, what we see in quotes across Western Europe and the US. They are orientation, not a price list: a scope note changes the number more than the app type does.

All ranges assume one language, one country's legal requirements and no legacy data migration. Servers, domains and third-party APIs — SMS, payments, maps — are paid separately.

What Pazl charges

Our starting prices are published on the service pages, and each one is a fixed project price for an agreed first version:

The final number depends on the screens, integrations and roles in your first version. Third-party fees and running costs — store accounts, payment and push providers, hosting — are listed in the proposal, not discovered after launch.

How long it takes, and why time is money

Most studios work in phases. For a mid-size mobile app, a realistic breakdown looks like this:

• Discovery and specification (1–3 weeks). Requirements, architecture, wireframes. This is where scope gets fixed; skipping it is the most common reason projects go over budget.
• Design (2–4 weeks). Screens, components, a clickable prototype and review rounds.
• Development (6–16 weeks). Backend and app built in parallel.
• Testing (2–4 weeks). Real devices, slow networks, payment flows in sandbox mode.
• Store submission (1–2 weeks). Both stores review every app; payments, health data and children's apps get stricter checks.

A smaller first release is faster. At Pazl, a small release can be planned from around five weeks once the scope, content and access are ready; integrations, custom features and store reviews extend that. The delivery date is written into the agreement.

Hidden and running costs most budgets miss

The build is the one-off cost. An app then costs money every month.

• Store accounts. The Apple Developer Program costs $99 a year; Google Play charges a one-time $25 registration fee (Apple Developer Program and Google Play Console help pages; check them before you budget). Apple's organisation enrolment requires a D-U-N-S number, so open the accounts in week one, not in the week of launch.
• Third-party services. SMS for sign-in codes, maps, analytics and push notifications are billed by usage. A loyalty app that sends a lot of SMS pays for every message; push notifications are usually far cheaper.
• Hosting and monitoring. Servers, databases, backups and error tracking.
• Updates. Apple and Google release new OS versions every year and raise their technical requirements. An app nobody updates starts breaking.
• Support and small changes. Bug fixes outside the warranty, new offers, a changed menu. Budget a monthly amount or agree a support plan; we describe a sensible set-up in product support after launch.
• GDPR. If the app collects personal data from EU users, you need a privacy policy, a lawful basis for each data type and data processing agreements. Fines under the GDPR can reach 4% of global annual turnover or €20 million, whichever is higher (Regulation (EU) 2016/679, Art. 83). Build it into the spec from day one.

How to cut the budget without cutting quality

The cheapest hour is the one nobody has to work. Scope decides cost more than rates do.

1. Start with one journey. Ordering, loyalty or booking — not all three. The second journey is cheaper once you know which one customers use.
2. Check whether you need an app at all. If customers use it less than once a month, a web app or a messenger mini app may do the job for a fraction of the price. See how to make an app for your business for how to decide.
3. Build cross-platform unless a native feature really requires two codebases.
4. Reuse proven modules for sign-in, payments, push and admin, and spend the budget on what makes your app different.
5. Plan integrations early. An API that turns out to be missing in week eight is the most expensive surprise in app development.
6. Prepare content and accounts early. Late menus, photos and store accounts delay launches more often than code does.

Fixed price or time and materials?

Fixed price works when the scope is written down before development. You know the number, the vendor carries the risk of underestimating, and changes go through a documented change request. It forces clarity up front.

Time and materials works when requirements are genuinely uncertain. You pay for hours worked, which gives flexibility but moves the cost risk to you. Without a budget cap and regular reports, the final bill is hard to predict.

At Pazl we work at a fixed price: the scope, price and delivery date are agreed in writing before development starts. Why the numbers hold is explained in fixed-price software development: how we make the numbers hold.

Common mistakes that inflate app budgets

• Comparing quotes for different scopes. A €10,000 quote without an admin panel and a €30,000 quote with one are not two prices for the same app.
• Leaving the admin panel for "later". The app goes live, and nobody can change prices or offers without a developer.
• Paying by the hour with no cap. Flexible billing without a budget ceiling is how estimates double.
• Ignoring store rules. An app that is only a website in a wrapper can be rejected, and a rejection adds time.
• No budget for version two. The first release shows what users need. If all the money went into version one, you cannot act on it.

Checklist: what to ask before you sign

• What exactly is included: design, backend, admin panel, integrations, store submission, warranty?
• Is the price fixed, and how are changes priced?
• Who owns the code, the design files and the store accounts after the final payment?
• What does the warranty cover, and for how long?
• Which running costs will we pay each month, and to whom?
• Who reviews the code, and what happens if a key developer leaves?
• Can we open an app you have shipped, not only see screenshots?

What we have built

Two examples from our work show where the budget goes. For a beverage retail chain we rewrote an outdated app from scratch, migrated the customer base and added a loyalty programme with an Apple Wallet card, push offers and an admin panel for promotions — the chain reported +28% repeat purchases and +17% revenue from promotions (case study). For a logistics company we built one web system for fleet monitoring, documents and finance with separate interfaces for each role, GPS tracking and a Telegram bot for drivers (case study). In both cases most of the work was behind the screen: data, integrations and admin tools.

Frequently asked questions

How much does it cost to build an app for a small business?

A focused first version — one main journey, iOS and Android, an admin panel — usually sits at the lower end of the ranges above. At Pazl it starts from €4,750 at a fixed price. Integrations, extra roles and custom design move the number up.

What is the biggest factor in app development cost?

Scope: the number of journeys, roles and integrations. The choice between iOS, Android and both matters less than people expect, because most business apps are built cross-platform from one codebase.

How much does it cost to maintain an app?

Plan for store fees, hosting, third-party services billed by usage and a budget for updates and small changes every year. The exact amount depends on your users and integrations; a good proposal lists these costs before you sign.

Is a cheaper app from a freelancer a good idea?

It can be for a small, well-defined app. The risks are a single point of failure, no second reviewer and unclear ownership of the code and accounts. Whoever you hire, get the scope, the price and the ownership in writing.

Why do app quotes differ so much?

Because vendors estimate different things. One assumes a template and no admin panel; another includes custom design, integrations, testing on real devices and support after launch. Ask each vendor what is included and excluded.

Should I build a web app first to save money?

Often, yes. A web app runs on every phone without store review, and the same backend can later power a mobile app. A native or cross-platform app is worth it when users need push notifications, offline use, the camera or a wallet card in the core flow.