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

What does an app cost to build?

App costs span a wide range, so start with what the market reports and then price your own scope. Clutch, a B2B review platform, said in its October 2026 pricing guide that most app projects reviewed on its platform fell between $10,000 and $49,999, that the average project cost was $90,780, and that a typical project took about 11 months.

Read those figures with care. Clutch says its data comes from verified client reviews but doesn't publish a sample size, and the gap between the most common bracket and the average shows a long tail of large projects. Its listed hourly rates for app development companies, $25 to $49 an hour, also reflect where many reviewed firms are based: the same guide lists rates from under $25 in India to $100 to $149 in Australia.

For a sense of US labor costs, the U.S. Bureau of Labor Statistics put the median pay for software developers, quality assurance analysts and testers at $134,040 a year, or $64.44 an hour, in May 2025. Agencies and freelancers bill above wages because they also cover unbilled time, tools and overheads.

Whoever you hire, app cost comes down to one equation:

Cost = (features × platforms) + back end + design + testing + store setup, then maintenance every year.

The rest of this guide takes each part in turn.

Is a native or cross-platform app cheaper?

A cross-platform app is usually cheaper, because one codebase runs on both iOS and Android. Native apps, built separately in each platform's own language, cost more to build and maintain but give the deepest access to device features and platform conventions.

For most businesses, a cross-platform build is the sensible default. Go native when the app depends on something cross-platform can't do well, and prove that early with a small technical test rather than an assumption.

Which features drive the cost of an app?

Features, not screens. A screen that shows a list is quick; the logic behind it, such as payments, permissions, sync and notifications, is where the hours go. Use this table to see which features in your wish list carry the most effort.

Two lines in that table surprise most buyers. Offline mode is one of the most expensive features because the hard part is not storing data but resolving conflicts when the phone reconnects. And the admin dashboard is often a second product: your staff need somewhere to manage bookings, users and content.

Why does the back end matter so much?

Because most of an app's work happens on servers, not on the phone. The back end stores data, enforces who can see what, sends notifications, takes payments and talks to your other systems. In many business apps, it is as large a job as the app itself.

A back end typically includes:

• A database and API that the app reads and writes.
• Authentication and permissions, so a customer sees only their own bookings and a technician only their own jobs.
• Integrations with the systems you already run, such as a CRM, scheduling or accounting tool.
• An admin area for your team.
• Hosting, monitoring, backups and security updates, which continue every month.

If you already have software with a documented API, the app can often reuse it, which saves a large share of the cost. If your data lives in spreadsheets or an old system with no API, budget to fix that first. Our guide to custom software vs off-the-shelf covers how to decide what to build and what to keep.

How much does design add to the cost of an app?

Design is a smaller line than development but decides whether people use the app. Expect discovery and user research, flows and wireframes, a clickable prototype, visual design for both platforms' conventions, and accessibility checks.

Spend on design early: changing a prototype costs hours, while changing a finished app costs weeks. Test the prototype with five or six real customers or staff before a line of production code is written.

What fees do the App Store and Google Play take?

Publishing costs little. Commissions apply only to digital goods sold inside the app, and many business apps sell none.

Google Play's fee page, as read in October 2026, describes a new structure that began on June 30, 2026 for users in the US, EEA and UK, and on September 30, 2026 in Australia and Japan. It separates subscriptions from other purchases, distinguishes new installs from existing ones, and adds a 5% billing fee when Google Play Billing is used; auto-renewing subscriptions, for example, carry a 10% fee plus the 5% billing fee on the first $1 million of annual earnings. Store terms change and differ by country, so check both stores' pages before you set prices.

The rule that matters most for service businesses: Apple's guideline 3.1.3(e) says apps selling physical goods or services consumed outside the app must use payment methods other than in-app purchase. Google Play's payments policy says the same for physical goods and services such as cleaning or transportation. A booking app for a salon, a delivery app for a restaurant or a field-service app for technicians takes payment through a normal payment provider, without a store commission on those sales.

What does an app cost to maintain?

More than most buyers expect, and every year. An app is never finished: the platforms change under it.

Both stores set rules that force regular updates:

• Apple. Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK or the matching SDK for other Apple platforms. Apple has raised this minimum before, for example to Xcode 15 in April 2024.
• Google Play. From August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher, with extensions available to November 1, 2026. Existing apps that target Android 14 (API level 34) or lower stay available to new users only on devices running the same or an older Android version.

On top of store rules, budget for:

• Hosting, monitoring, backups and security patches for the back end.
• Updates to the framework and third-party libraries the app uses.
• Fixes when a connected system, such as a payment provider or CRM, changes its API.
• Testing on new devices and screen sizes.
• Small improvements once real users show you where they get stuck.

Ask any developer for a yearly maintenance figure in writing, what it covers and how fast security fixes are applied.

Do you need an app or a website?

Many businesses that ask about an app need a fast, well-built mobile website instead. Apple's own guideline 4.2 says an app should offer features, content and interface that go beyond a repackaged website. Use this table to decide.

Examples help. A gym's members booking classes every week, a property manager's tenants reporting repairs with photos, and technicians closing jobs offline all point to an app. A law firm taking new enquiries, a restaurant showing a menu and a consultancy publishing its services point to a website; see how much a website costs for that route. Some businesses need both: a website to win customers and an app or a client portal to serve them.

How can you lower the cost of building an app?

Build the smallest version that solves one real problem, then grow it with evidence.

1. Start with one workflow. Booking, ordering or job completion, not everything at once.
2. Choose cross-platform unless a technical test proves you need native.
3. Reuse what you have. Connect to your existing systems through their APIs instead of rebuilding them.
4. Buy the standard parts. Payments, sign-in, maps and messaging are better handled by proven services.
5. Fix the scope. A written feature list with must-haves and a later list keeps the budget honest.
6. Agree targets before the build. Bookings made in the app, calls avoided, jobs closed same day. Measure the baseline first.

If you're weighing an app, see how Worcia builds mobile apps for iOS and Android, and the custom software, from back ends to admin dashboards, that sits behind them.