Ask five UK agencies what an app costs and you will get answers ranging from £5,000 to £250,000, often for what sounds like the same brief. Neither end is lying. The spread exists because "an app" describes a category as broad as "a building", and the price depends on decisions most buyers have not been asked to make yet.
This guide gives you the real UK numbers for 2026, explains what actually moves the price, and covers the ongoing costs that agencies mention quietly on page nine of the proposal. By the end you should be able to read a quote and know whether it is honest.
The short answer
- No-code or template build (Glide, Adalo, FlutterFlow): £3,000 to £15,000 to launch, plus platform fees of £30 to £250 per month. Fine for internal tools and proving demand. Fragile beyond that.
- Cross-platform build (React Native, Flutter): £25,000 to £70,000 for a well-scoped first version serving both iOS and Android from one codebase.
- Native build (Swift for iOS, Kotlin for Android): £40,000 to £120,000 or more for a first version, and roughly double the ongoing cost if you need both platforms built separately.
- Web app or PWA instead of a native app: £15,000 to £50,000, no app store gatekeeping, one codebase, instant updates. For a large share of business ideas this is the right answer and nobody pitched it to you.
Complex products - marketplaces, anything with real-time features, regulated fintech or health data - sit above all of these bands, commonly £100,000 to £300,000 for a serious first release.
If a UK agency quotes £5,000 for a custom native app, you are buying a template with your logo on it. That can be a legitimate purchase, as long as you know that is what it is.
What actually drives the price
App quotes are mostly a function of five things. When you see a wide spread between agencies, it is usually because each has assumed something different about one of these.
1. Number of screens and states
A screen is not one design. A bookings list has a loading state, an empty state, an error state, an offline state and a populated state. A 12-screen app is realistically 40 to 60 designed and built states. Agencies that quote low often price the happy path only, and the difference surfaces later as change requests.
2. Accounts and authentication
An app with no login is dramatically cheaper than one with accounts. The moment you add users you add registration, sign-in, password reset, session handling, account deletion (an App Store requirement), and usually email infrastructure. Social sign-in and two-factor add more. Budget £4,000 to £10,000 of the total for doing accounts properly.
3. Payments
Taking money means Stripe or a similar processor, webhook handling, refunds, receipts and edge cases like failed renewals. In-app digital purchases also mean Apple and Google taking 15 to 30 percent and a stricter review process. Physical goods and services can use standard card payments and avoid the store commission entirely - an important distinction that affects both cost and margin.
4. The backend nobody sees
Most of an app is not the app. It is the server, database, APIs, admin dashboard and notification infrastructure behind it. On a typical build, 40 to 60 percent of the budget goes on the backend. A quote that seems too good has usually assumed your backend already exists or barely needs one.
5. Offline, real-time and device features
Offline support with syncing, live updates (chat, tracking, availability), camera and location features, and background processing each add genuine engineering. None is exotic, but each one you tick adds thousands, not hundreds.
UK rates vs offshore: the honest trade-off
UK agency day rates in 2026 typically run £400 to £900 per day depending on seniority and region. Offshore teams advertise £100 to £250 per day, which looks like a 70 percent saving.
Sometimes it is. Often it is not, for reasons that only show up mid-project:
- Specification burden shifts to you. Offshore delivery is only as good as the written spec, and most SMEs have never written one. Ambiguity gets resolved by guessing, and reworking guesses costs the savings back.
- Communication overhead is real. Time zones and language friction turn a two-minute question into a next-day answer, and a three-month project into six.
- Code quality is invisible until you leave. The cheapest builds are often unmaintainable, and the second agency's first job is a rebuild. We have inherited enough of these to say it plainly: the most expensive app is a cheap one built twice. The maths is the same as with websites, which we covered in the true cost of a cheap website.
A middle path many UK businesses land on: a UK team responsible for architecture, product decisions and quality, at a fixed price, so the risk of the spec sits with people you can meet.
The ongoing costs agencies undersell
The build price is not the price. Owning an app carries running costs that you should have in the spreadsheet before you commit:
- Apple and Google developer accounts: £79 per year and a one-off £25 respectively. Trivial, but a prerequisite.
- Hosting and infrastructure: £50 to £500 or more per month depending on usage, plus third-party services (maps, SMS, email, analytics) that scale with users.
- Maintenance and OS updates: iOS and Android each ship major versions every year, and things break. Budget 15 to 20 percent of the build cost per year to keep the app healthy, secure and accepted by the stores.
- Feature iteration: the first release is a starting point. Apps that win their category ship improvements continuously; apps that launch and freeze slide down the store rankings and the review scores follow.
If the ongoing line was missing from a proposal you are comparing, add roughly 20 percent of build cost per year to it before comparing totals.
Do you actually need a native app?
This is the question that saves more money than any negotiation. Native apps earn their cost when you genuinely need what only native provides: push-heavy engagement, offline-first workflows, deep device integration, or a store presence your customers expect.
A large share of briefs we see need none of that. They need a fast, installable web application that works on every device, updates instantly, and skips the store commission and review queue entirely. We wrote a full decision framework in do you actually need a mobile app? - read it before you spend five figures, because the honest answer is sometimes the cheaper one.
Questions to ask any app agency
Take these into every sales conversation:
- Can I see two apps you have shipped that are live in the stores today, and can I speak to those clients?
- What is included in the price for backend, admin dashboard and analytics, and what is assumed to exist already?
- Which states are covered: loading, empty, error, offline, or just the happy path?
- Who owns the code and the developer accounts, and what do I receive if we part ways?
- What does the first year of maintenance cost, itemised, and what does it cover?
- What would you cut from my brief to hit a smaller budget, and what would you refuse to cut?
That last question is the best filter we know. A good agency will happily trim scope and will defend the things that protect you. An order-taker will just say yes to everything until the invoices arrive.
The bottom line
In 2026 a credible UK price for a well-built first version is roughly £25,000 to £70,000 cross-platform, more for native or complex products, plus around 20 percent per year to run and improve it. Quotes far below that are quoting a different product than the one you described. And for many businesses the best-value answer is a web platform, not a native app at all.
We build native iOS apps in Swift and web platforms in Next.js, and we will tell you which one your brief actually needs - including when the answer is the cheaper one. See our pricing for how we structure fixed-price builds, or talk to us about your idea and we will give you a straight number.