How Much Does It Cost to Make an App in 2026?

Ask five agencies to quote the same app and you will get five numbers spread across an order of magnitude. That is not because four of them are lying. It is because the phrase "an app" covers everything from six screens over a spreadsheet to a regulated payments product, and because most of the spread comes from two variables nobody puts in the proposal: where the team sits and how much of the work the quote quietly leaves out. Here are the real numbers, where they come from, and what to do with them.

The short answer

These are worked figures for a team in Central or Eastern Europe, which is the most common choice for founders outside the United States and a useful midpoint. Multiply by roughly three for North America and by two for Western Europe.

The ranges are wide on purpose. A specification always moves once work starts, and any estimate presented as a single number is either padded or about to be renegotiated. You can reproduce all of these, and change any assumption, with our website and app cost calculator, which uses exactly the model described below.

What actually drives the number

Four things, in descending order of impact.

• Where the team sits. Blended rates run from about $20 an hour in South and Southeast Asia to $180 in North America. Nothing else in this list moves the total by a factor of five.
• Screen count. Budget roughly 30 hours per screen on top of a 300 hour base for the shell, navigation, state, build pipeline and store setup. That base is why a two screen app is not cheap.
• Design depth. A template based design multiplies effort by about 0.85, a custom design by 1.0, and a bespoke design with a proper design system by 1.3. The system costs more once and pays back from the second product onwards.
• Integrations. Fixed hours land on top: accounts and login about 35, payments 40, a third party API 25, an admin dashboard 80, AI features 60. Anything touching money or identity carries compliance and edge cases, which is why it is priced separately.

The second platform is the variable people misjudge most often. Shipping iOS and Android is not double. Discovery, design, backend, API work, QA planning and management are shared, so only the client layer is duplicated. In practice that is about 60 percent more, not 100.

Why the same app costs five times more elsewhere

Blended means the average across seniors and juniors on the team, not the rate of the person writing the code. Two proposals quoting the same headline rate can still differ by half if one plans a senior heavy team and the other plans one lead and three juniors. That is the question worth asking in the first call, and it is one of several covered in our guide to choosing a software development company.

The cheapest region is not automatically the best value. Time zone overlap, English fluency and how much management you have to supply yourself all show up as real cost on your side of the table, which is the trade we work through in the outsourcing guide.

Where the money goes

A healthy app project splits roughly like this. If a quote is missing three of these six lines, it is not cheaper, it is incomplete.

• Discovery and planning, 8 percent. Flows, scope, technical decisions. The cheapest hours in the project and the ones most often cut.
• Design and UX, 18 percent. Screens, states, the empty and error cases everyone forgets to draw.
• Client build, 30 percent. The app itself, per platform.
• Backend and integrations, 24 percent. API, data model, third party services, push notifications.
• QA and testing, 12 percent. Devices, operating system versions, store review readiness.
• Project management, 8 percent. Someone has to run it. If nobody is quoted for this, you are that person.

The costs nobody quotes

The build number is the part everyone talks about and rarely the part that surprises them a year later.

• Upkeep, 15 to 20 percent of the build cost per year. Both mobile platforms ship breaking changes annually, dependencies need patching, and store policies move. An app left alone for eighteen months is a rewrite, not an asset.
• Store fees. The Apple Developer Program is $99 per year. Google Play is a one time $25 registration.
• Backend hosting and monitoring. Small at first and rarely zero. Push notification services, crash reporting and analytics all have paid tiers you reach faster than expected.
• Content and data migration. Getting real content and real users out of an old system is almost never in the estimate.
• The second round of design. Nearly every app gets a meaningful revision within a year of launch, once actual behaviour contradicts the plan.

How to spend less without wrecking it

The effective lever is scope, not rate. Cutting the rate buys you a cheaper hour; cutting scope buys you fewer hours and an earlier answer about whether the thing works.

• Ship one platform first. Pick the one your users actually hold. Half the client cost, all of the learning.
• Six screens, not twenty. The base cost is fixed, so the saving comes from screens. Most first versions carry at least a third of screens that never get used.
• Design on a system. A component library beats inventing every screen and it pays back from the second release.
• Defer money and identity. Payments, accounts and anything regulated carry the most hours and the most risk. Validate demand before you build them.
• Consider cross platform. One codebase compresses the client layer, at the price of friction where you need deep platform specific features.
• Do not cut QA or discovery. They are 20 percent of the budget between them and they are the two lines that prevent the expensive kind of rework.

One architectural note worth adding, because it shows up in the backend quarter of the budget: do not start a small product on a distributed architecture. The operational overhead is a monthly cost with no user facing benefit at that size, a trade we lay out in microservices versus monolith.

Questions people ask

How much does it cost to make an app in 2026?

A lean first version of about six screens on one platform runs roughly $12,000 to $35,000 with a Central or Eastern European team. A typical twelve screen app on one platform lands between $20,000 and $56,000, and between $31,000 and $89,000 if you ship both platforms. The same app built in North America runs $90,000 to $247,000.

Does building for both platforms double the cost?

No, budget about 60 percent more. Discovery, design, backend, QA planning and management are shared, so only the client layer is genuinely duplicated.

What is the cheapest way to get a real app shipped?

Cut screens, not quality. One platform, a design system rather than bespoke screens, and nothing touching money or identity until version two.

What ongoing costs come after launch?

Between 15 and 20 percent of the build cost per year, plus $99 a year for the Apple Developer Program and a one time $25 for Google Play.

Why do quotes for the same brief differ by a factor of five?

Blended rate first, then design depth, then what the quote silently excludes. Discovery, project management and QA are about a quarter of the real effort between them.