How much does it cost to build a mobile app in 2026?

Ask ten agencies what an app costs and you will get ten variations of "it depends, let's book a call." That answer is not wrong — it genuinely does depend — but it is usually a stalling tactic, because the honest version of "it depends" is a short list of things you can be told up front.

So here is the list, and the numbers.

The price bands

These are the bands we quote in, and they are broadly consistent with what competent small studios charge. They assume a senior engineer doing the work, a fixed quote agreed before the build starts, and the client owning the code at the end.

The thing worth internalising: above roughly $60,000 you are usually not paying for the app. You are paying for organisational scale — procurement, compliance sign-off, integration with systems nobody has documented since 2014, and the coordination cost of a large team. Those costs are sometimes unavoidable and genuinely earned. They are just not the same product as "an app."

The five things that actually move the number

1. Screens, but only sort of

Screen count is the metric everyone reaches for, and it is the weakest one. Twenty screens that display data cost less than four screens that edit it, because editing means validation, conflict handling, optimistic updates, and error states nobody thinks about until they appear. Count interactions, not screens.

2. Whether it needs a backend you don't have yet

This is the single most common reason a quote doubles. "Just an app" almost always means an app plus an API, a database, authentication, file storage, an admin view for your own team, and somewhere to run all of it. If that infrastructure doesn't exist, it is roughly half the project. If it does exist and is documented, the app gets much cheaper.

3. One platform or two

Native iOS and Android are two codebases. React Native is one, and typically saves 30–40% against building both natively. That saving is real for most apps — and it evaporates for a specific class: apps leaning on platform-specific hardware, deep OS integration, sustained high-frame-rate graphics, or Bluetooth Low Energy edge cases. In those, debugging through an abstraction layer costs more than writing native code twice. We build both ways and choose per project; anyone who always recommends the same one is telling you about their staffing, not your app.

4. Integrations you don't control

Every third-party system is a risk premium, and the premium scales with how well it is documented. A modern REST API with a sandbox is nearly free to integrate. A payment provider is a day. A legacy system speaking a serial protocol from the 1990s with no documentation is a discovery project wearing an integration's clothes — we have done exactly that one, and the honest way to price it is to scope the unknown separately rather than pretend it's a line item.

5. Who is actually writing the code

The largest variable, and the least visible. The same brief priced by a senior engineer and by an agency staffing three juniors under a delivery manager produces wildly different numbers — and the cheaper quote is frequently the more expensive project, because rework is invisible until it isn't. Ask who writes the code. Ask to see something working in week one.

Why the same brief gets quoted at $8,000 and $250,000

Not because one vendor is honest and the other is fleecing you. Usually because the brief was underspecified and each vendor priced a different imagined scope. One assumed you had a backend; one assumed they were building it. One quoted one platform; one quoted two plus a web admin. One assumed you owned the designs.

A quote is only comparable to another quote when both name the same things. Before you compare, get every vendor to write down:

• The exact screen list, and which screens write data rather than only read it
• Which platforms, and native or cross-platform
• Whether the backend is included, or assumed to exist
• Every third-party integration, named
• Who owns the code, the repository, and the developer accounts at the end
• What happens after launch, and what that costs

Two quotes against that list are comparable. Two quotes against "a fitness app" are not.

What almost every quote leaves out

These are not scams; they are conventions, and they surprise people anyway. Ask about each in writing:

The developer accounts matter more than their price suggests. If your app ships under someone else's Apple account, you do not really own your app. Insist on your own accounts from day one.

What we charge, since it would be strange not to say

Norward quotes mobile apps from $4,500, typically 3–6 weeks, fixed price agreed before the build starts, with a working demo every week and the full source in a repository you own. Projects are split into milestones — a deposit to start, a mid-point payment, and the balance at launch.

We can price that way for the same reason the bands above have moved at all: a senior engineer working with AI agents produces what a small delivery team used to. The agents handle volume — scaffolding, tests, boilerplate, first drafts. The human owns the architecture and reviews everything that ships. That is how the work actually runs, and it is why fixed quotes are possible at all: the estimate variance that made hourly billing necessary has narrowed.