App development cost UK: prices, scope and ongoing costs

How much does it cost to develop an app in the UK? Clutch’s UK pricing guide gives an initial range of £30,000–£80,000 for MVPs or apps with limited features, rising to £80,000–£200,000 for apps of medium complexity. Enterprise or regulated builds can cost £200,000 or more. The features, platforms, integrations and work included in the quote determine where a project fits.

The harder part is understanding what those figures actually cover. Two teams might quote for the same app idea and include very different amounts of work. To help you compare them, we’ll look at what belongs in an estimate, what pushes the price up and what to budget for after launch, including where AI can help your money go further.

In this guide: UK prices · quote inclusions · price factors · AI and your budget · timelines · after launch · your next step

Updated 8 October 2026. Originally published 7 February 2023.

App development cost UK: prices, scope and ongoing costs

How much does app development cost in the UK?

A simple app usually does a few things well for a clearly defined audience. As you add more user roles, connected systems or demanding device features, there’s more to design, build and test — which is where the budget starts to grow.

Project UK market range reported by Clutch What to clarify in the estimate
MVP or app with limited features £30,000–£80,000 Essential journeys, agreed platforms, design, backend, testing and launch
App of medium complexity £80,000–£200,000 Integrations, payments, dashboards and the work needed to connect them
Enterprise or regulated app £200,000+ Scale, specialist requirements, connected systems and release criteria
Prototype or existing-app improvement Price the defined stage individually The journey to test or improve, affected systems and rollout requirements

Source: Clutch’s UK app development guide, checked on 8 October 2026. These are published market ranges rather than a single UK average or Fortnight’s rates. Prototype and improvement work is listed separately because a whole-app range does not price a smaller stage.

For a broader comparison, Goodfirms’ 2026 research combines insights from 267 companies with published benchmarks across North America, Europe and Asia. Its international estimates cover different markets and project categories, so they should not be treated as UK prices.

Once you have a starting budget, compare proposals against the same requirements, with VAT, third-party fees and exclusions clearly explained. If a complete new app is beyond your budget for now, a prototype or a focused improvement may still be a useful first step.

What should an app development quote include?

A quote should let you see how the team plans to take your idea through to a working product. These five areas are a good place to start:

  • Discovery and design: product decisions, user journeys, wireframes, prototypes and any user research or testing.
  • Development: iOS and Android coverage, backend, database, admin tools and integrations.
  • Testing: supported devices, error handling, performance and acceptance criteria.
  • Launch and handover: store submission, account ownership, source code, design files and documentation.
  • Project management, commercial terms and support: coordination and progress reviews, payment stages, how changes are priced, covered fixes, ongoing support and third-party fees.

Even if a proposal says “MVP”, it’s worth checking whether that includes the backend, staff tools and store submission. The label alone won’t tell you who’s responsible for each part.

Some work will need a closer look before it can be priced reliably. If your app connects to an existing booking system, for example, the team may need access first. A useful proposal makes that dependency clear and tells you when the price can be confirmed.

How to compare two app quotes

With the same brief in front of both teams, you can compare what they’ve actually allowed for. Mark platforms, design, backend, admin tools, integrations, testing, launch and support as included, excluded, assumed or priced later. You’ll spot gaps much more easily than by comparing the two totals alone.

With a fixed price, agree the deliverables and how changes will be handled. With time and materials, agree rates, a spending limit or review point, and regular demonstrations of completed work. If important questions remain open, a discovery phase can help define the release before committing to the full build.

Our questions to ask when you receive an app quote can help you work through a proposal.

What changes the cost of an app?

User journeys and roles

Take an appointment-booking app: customers need to choose a slot, staff need to manage availability, and administrators may need to control permissions. Each person uses the product differently, so the estimate needs to cover those journeys and their testing. Counting screens won’t capture all of that work.

Backend and integrations

Behind those journeys, your app may need to store bookings, synchronise data or connect to payments, maps and existing business systems. How easily the team can work with those systems matters too: clear documentation and test access give them a much better basis for an estimate.

Behaviour when things go wrong

What happens if a slot disappears just as someone books it, or their connection drops halfway through? Those situations are part of making the booking journey work. They need time for design, development and testing, even though they may never appear in the initial screen list.

Design readiness

When a tested prototype covers the complete journey, developers have a clearer starting point. If error, loading or empty states are missing, those decisions still have to be made during the build. This is part of the work covered by our UX/UI design services, from research and flows through to developer handover.

Specialist requirements

Sensitive data, accessibility, offline use and demanding device integrations can increase the work. Agree the requirements, relevant assessments and responsible specialists before finalising the budget.

The team and delivery model

It also helps to know who’s behind the estimate. Experience, location and the mix of design, engineering, testing and project management all affect the price. A lower hourly rate may look attractive, but the final bill also depends on how long the work takes and whether key roles are charged separately.

iOS, Android or cross-platform: what changes the budget?

Start with the people who’ll use the app and the capabilities they need. That gives you a better basis for choosing platforms than price alone.

Approach When it may fit Budget implications
iOS or Android first Your initial audience can be served on one platform A narrower first release; adding the other platform needs a separate estimate
Cross-platform Both audiences need similar features and journeys Shared code can reduce duplicate implementation; device testing and platform-specific work remain
Separate native apps The product needs extensive platform-specific experiences or device capabilities More separate implementation to build and maintain, with shared backend work scoped alongside it

Before settling on the technology, ask the team to assess your most demanding feature. Sharing code can reduce duplicate work, while testing and store preparation still need to cover both platforms. For a closer look at the options, see our native vs hybrid app guide.

The same idea, two different scopes

Let’s return to the booking app. To find out whether people understand the journey, a clickable prototype could use sample appointments and simulated responses.

To take real bookings, though, a working first release needs live availability, stored data, connected services and a way for staff to manage appointments. The team also has to test what happens when something goes wrong.

In this illustrative example, both could be described as an “appointment app”. The difference is what you need from them: one helps you test the idea, while the other has to handle real bookings. That difference belongs in the estimate.

How we turn an app idea into an estimate

At Fortnight, we bring design and development into that discussion together. For a booking product, we’d look at how customers use it alongside the availability, staff tools and systems needed to make it work. From there, we can define the proposed release and identify what still needs resolving before we estimate it.

How to keep your app development budget focused

One practical way to keep the budget focused is to build a complete core journey and leave optional features for later. Established components and managed services can help where they fit, provided you also check their recurring charges and any limits on customisation or moving your data.

How AI can make your app development budget go further

With an experienced team, AI can help your budget stretch further. When less time goes into repetitive implementation and documentation, there may be more room to improve a journey, test an idea or act on feedback before launch. The value comes from choosing useful work for that extra capacity.

Here’s where AI assistance can fit into an app project:

Work How AI can help Where the team still needs to apply its judgement
Routine implementation Draft repetitive code and standard components Architecture, correctness, security and maintainability
Testing Draft test cases and suggest edge cases Whether tests cover real user journeys and catch meaningful failures
Documentation Prepare drafts of technical explanations and handover notes Accuracy against the product and code being delivered
Working with an existing app Help locate relevant code and explore possible changes Dependencies and the effect on the working product

For our booking-app example, time saved on suitable tasks could give the team room to test self-service rescheduling, improve the booking flow or check more thoroughly for duplicate bookings. Each option still needs its design, development and testing considered together, so the next step is to decide which would make the biggest difference for users.

The gains vary with the task and codebase. McKinsey’s 2023 experiment found faster completion of several coding tasks; METR’s February 2026 follow-up could not reliably establish the size of gains with later tools. Neither gives you a percentage to deduct from every app budget.

When discussing your project with us, ask where AI assistance could help and how we’d use any time saved. That might mean a shorter delivery schedule, more work within the agreed budget or a lower estimate for suitable tasks. What matters is connecting the tools to a useful, properly reviewed product.

How long does it take to build an app?

As a broad planning reference, Goodfirms’ global 2026 research lists 3–6 months for basic apps and 6–9 months for mid-level apps. These categories cover complete applications across several markets; they are not UK averages or Fortnight delivery commitments. A smaller prototype or tightly scoped MVP needs its own schedule.

For your own project, ask the team to map out discovery, design, development, testing and store submission. AI may shorten suitable production tasks, but the calendar also depends on feedback, access to connected systems and decisions still to be made. It’s worth agreeing what the target date means, too: a testable build, submission to the stores or a public launch. Store review comes after submission.

What does an app cost after launch?

Once the app is live, you’ll have provider bills, maintenance and future improvements to plan for. Separating them makes it easier to see what keeps the product running and what pays for its next stage.

Cost Starting reference What can change the total
Backend, database and storage Supabase Pro starts at US$25/month Compute, extra projects, storage and traffic
Transactional email Resend Pro costs US$20/month for 50,000 emails Sending volume and additional services
Other connected services Provider subscriptions and usage charges SMS, maps, payment processing and AI usage
Store accounts Apple: US$99/year; Google Play: US$25 once Local billing, applicable taxes and separate sales commissions
Maintenance and support A defined support agreement or agreed hours Updates, monitoring, fixes, response times and exclusions
New features Estimate each planned iteration Research, design, development and testing

Provider prices checked on 8 October 2026. They are examples for budgeting; the services your app needs will depend on its architecture and usage.

When comparing maintenance proposals, look at included hours × the quoted rate, or the work covered by a support contract. You’ll want to know which updates, monitoring and fixes are covered, how quickly the team responds and what happens if more work is needed. Those hours are separate from provider subscriptions, so agree who owns each account and pays its bills as well.

Getting the app in front of users takes a budget too. App-store assets, marketing content and campaigns may sit outside the development proposal, so check what’s included and allow for the rest separately.

Our guide to the hidden costs of mobile app development covers more of the costs to discuss before launch.

How much does it cost to update an existing app?

If your existing code and systems can support the changes, updating an app may cost less than starting again. But improving onboarding, adding a feature and redesigning the whole experience are very different jobs, so the estimate needs to reflect the change you’re making.

At Fortnight, we start with what you want to improve and a review of the existing product. That helps us work out the design, development and testing needed, including any changes to connected systems, so we can estimate the update you actually need.

Start with five answers

You don’t need a finished technical specification to start a conversation. If you can answer these five questions, you already have a useful starting point:

  1. Who is the app for, and what must they do? Describe the main user and their essential task.
  2. What should this stage deliver? Explain the result you need and what can wait.
  3. What already exists? Share the app, designs, research, code or systems the team will work with.
  4. What needs to be preserved or investigated? Include data, integrations, staff workflows and important unknowns.
  5. What are your budget and target date? Explain any deadline and why it matters.

Ready to plan your app? Share these five answers and discuss your project with us.

Fortnight service
Mobile apps design & development

Custom iOS and Android apps built for your business and your customers.

Explore the service →Or get in touch

Get new articles by email

New articles and studio updates from Fortnight, delivered to your inbox.

Subscribe

Thanks — you’re in. We won’t spam you, just share genuinely useful things.

By subscribing, you agree to emails from Fortnight. Unsubscribe anytime.

Read next

All articles