How Much a Mobile App Costs
Last updated:
Ranges, by shape of app
| App | Range | Duration |
|---|---|---|
| Content or catalogue, read-only | £25k–£45k | 10–14 weeks |
| Business app: accounts, forms, API | £45k–£80k | 14–20 weeks |
| Field app with offline sync | £70k–£130k | 18–26 weeks |
| Marketplace or booking with payments | £80k–£160k | 20–30 weeks |
| Real-time: chat, tracking, live data | £100k–£200k+ | 24–36 weeks |
These are for both platforms with a backend. A single platform saves perhaps 20–25%, not half, because the backend and design are shared regardless.
The four things that move the number most
- Offline capability. Adds 20–40%. Conflict resolution — two people editing the same record on different devices — is genuinely hard.
- Real-time. Live tracking, chat, presence. Persistent connections, reconnection handling, battery management.
- Payments. Compliance, refunds, reconciliation, failure paths, and store commission rules if you sell digital goods.
- Number of user roles. Each role is a set of screens, permissions and test cases.
Two apps described identically in a brief can differ by a factor of three, and the difference is almost always offline behaviour and roles rather than screen count.
What people forget to budget
- Developer accounts: about £80 a year for Apple, a one-off for Google
- Store assets — screenshots for several device sizes, an icon, a listing
- A privacy policy that accurately describes data collection, which both stores check
- Backend hosting, which continues forever
- Push notification infrastructure
- Crash reporting and analytics tooling
The running cost is not optional
Budget 15–25% of the build per year. Unlike a website, some of this is forced: annual OS releases, periodic minimum-SDK requirements, deprecated APIs and library updates.
- Two OS updates a year to test against, minimum
- Store policy changes, which arrive with deadlines
- Dependency and security updates
- Crash fixes for devices you never owned
- Backend maintenance and hosting
An app left untouched for two years typically needs a substantial rework to be publishable again. That is the cost of skipping maintenance, and it is usually larger than the maintenance would have been.
How to build the same idea for less
- One platform first — whichever your users actually hold
- Online-only in version one; add offline when you know which screens need it
- One role, not three
- Use the platform's own components rather than bespoke design everywhere
- Defer anything real-time; polling is fine at low volume and far simpler
The most effective single cut is offline. It is frequently requested for comfort rather than need, and it is the most expensive feature on most briefs.
Why quotes vary so widely
The same brief will get quotes from £15,000 to £150,000. The cheap ones are usually a template with no backend, or a team that has not scoped offline, payments or review.
Compare the exclusions, not the totals. Ask specifically: does this include a backend, an admin interface, store submission, and testing on real devices? The gap between two quotes is nearly always in those four answers.
Frequently asked questions
Can we build an MVP for under £20,000?
Do we pay Apple and Google a percentage?
Is it cheaper to add an app to an existing system?
What is the cheapest way to test an app idea?
Considering an app for your business?
Tell us how often a customer would open it. That one answer usually settles whether you need an app or a much cheaper mobile site.
Related services
What we build for problems like this one