Blog / 13 October 2026 / 5 min read
How much does it cost to build an app in the UK?
Typical UK price ranges for building a mobile app, what drives the cost up or down, and the ongoing costs to budget for after launch.
Joe
Director and Lead Software Engineer

App quotes can range from a few thousand pounds to several hundred thousand for what sounds like the same idea. That’s not because developers are making numbers up. It’s because “an app” can mean anything from a simple companion to a website to a full product with accounts, payments and real-time data.
Here are realistic UK ranges, what moves the price, and the costs that keep going after launch.
The short answer
These are typical ranges for a UK studio or experienced freelancer. Large agencies will usually be higher.
- Clickable prototype: roughly £3,000 to £10,000. Designed screens you can tap through on a phone, used to test the idea with real people before building it.
- Simple app (MVP): roughly £15,000 to £40,000. A focused first version that does one job well, often with sign-in and a simple backend.
- Established product: roughly £40,000 to £100,000. Subscriptions, notifications, richer data, admin tools and more polish.
- Complex platform: £100,000 and up. Real-time features, marketplaces, heavy integrations, offline support or strict security requirements.
What drives the cost
Number of screens and flows
Each distinct screen and journey (sign-up, onboarding, checkout, settings) needs designing, building and testing. A focused app with ten well-designed screens is much cheaper than a sprawling one with forty.
The backend
Most of an app’s cost often lives where you can’t see it: the server, database and APIs that store accounts and data. If you already have a platform with an API, the app can reuse it. If not, it has to be built.
One codebase or two
Building separate native apps for iOS and Android roughly doubles the work. Cross-platform frameworks like React Native let one codebase run on both, which is why they’re the default choice for most business apps. I’ll cover the trade-offs in a separate post on React Native versus native.
Payments and subscriptions
Selling subscriptions inside an app means following Apple’s and Google’s rules, handling trials, renewals and refunds, and keeping access in sync with your website. Tools like RevenueCat make this far easier than it used to be, but it’s still meaningful work.
Integrations
Every connection to another system (a CRM, a booking engine, a payment provider, an analytics tool) adds time. List them early.
Design
A polished, custom-designed app costs more than one built from standard components. For a consumer product that competes on experience, it’s usually worth it. For an internal tool, standard components are often fine.
The costs after launch
The build is only the start. Budget for:
- Developer accounts: Apple charges an annual fee for its developer programme and Google a one-off registration fee.
- App store commission: Apple and Google take a cut of in-app purchases and subscriptions, typically 15 to 30%.
- Hosting and services: servers, databases, push notifications, error monitoring and analytics.
- Maintenance: Apple and Google release new operating system versions every year, and apps need updating to keep working and stay in the stores. A common rule of thumb is 15 to 20% of the build cost each year.
How to spend less without cutting corners
- Prototype first. A clickable prototype is the cheapest way to find out what users actually want before paying to build it.
- Launch with less. Pick the one job the app must do brilliantly and leave the rest for version two.
- Reuse what you have. If your website already has accounts and data, build the app on the same backend.
- Go cross-platform unless you have a specific reason not to.
- Invest in release automation and monitoring. Being able to ship updates safely and often is cheaper than big, risky releases.
Getting an accurate quote
Describe who the app is for, the main things users need to do, whether you have an existing backend, and your budget and timeline. The same principles as writing a website brief apply.
I’ve taken mobile apps from first prototype to both app stores, including subscriptions and automated releases. If you’re planning one, tell us what you’re building and we’ll give you an honest range, including whether you need an app at all.