The short answer
App prices vary more than almost anything else in digital work. Two quotes for the “same” app can be thousands of pounds apart, because the word “app” covers everything from a loyalty card on a phone to a booking system with staff logins, payments and a dashboard.
The easiest way to make sense of it is to sort apps into three levels.
| Level | What it is | Typical starting cost | Our fixed price |
|---|---|---|---|
| Simple web app | Installs from your website onto any phone. Bookings, loyalty, menus, forms, notifications. | Around £5,000 | £4,995, up to 6 screens, live in 2 weeks |
| Native app | In the App Store and Google Play. Customer accounts and payments. | Around £10,000 | £9,995, up to 15 screens, live in 4 weeks |
| Full platform | iPhone, Android and web, with an admin dashboard and links to your other systems. | Around £20,000 and up | £19,995, up to 30 screens, live in 6 to 8 weeks |
Projects beyond that, such as marketplaces, apps with live video or anything handling medical or financial data, are priced individually and can run well into six figures with larger agencies.
What actually drives the cost
The price of an app comes down to how much has to be designed, built and tested. These are the factors that move it most.
Number of screens
Every screen needs designing, building and testing on different phones. A loyalty app might need six screens; a booking app with accounts, history and settings can easily need fifteen. Counting your screens on paper before you ask for quotes is one of the most useful things you can do.
Accounts and logins
As soon as customers have accounts, you need sign-up, login, password reset, account settings, and somewhere secure to store their data. That adds work and some UK GDPR responsibilities.
Payments
Taking card payments in an app means linking to a payment provider such as Stripe, handling refunds and failed payments, and following the app stores’ rules on what can be sold in-app. Apple and Google take a commission on some kinds of in-app purchase (typically digital goods and subscriptions), so check which rules apply to what you sell.
Admin tools for your team
Customers see the app; your team needs a way to manage it. An admin dashboard for bookings, orders, content or customers is often as much work as the customer-facing app.
Links to your existing systems
Connecting to your till, booking software, accounts package or CRM depends on whether those systems have a good API. A well-documented API makes it straightforward; an older system without one can add a lot.
Native or web
A native app is built for the App Store and Google Play. A web app (often called a progressive web app, or PWA) runs in the phone’s browser but installs to the home screen like an app. Web apps cost less because they are built once and need no store approval, but they have fewer phone features, and some features, such as push notifications on iPhone, have more limits.
Web app or App Store app?
A lot of small businesses assume they need to be in the App Store. Often they do not.
A web app is usually enough if:
- Customers mainly use it to book, order, check a loyalty balance or read information
- You can send people to it from your website, emails and QR codes
- You want to change things without waiting for store approval
An App Store app is worth it if:
- Customers will search the App Store or Google Play to find you
- You need deeper phone features such as background location, Bluetooth or advanced camera use
- Being in the stores matters for credibility in your market
A sensible route is to start with a web app, prove people use it, then move to the stores. Much of the work can carry over, particularly the back end: the database, the admin tools and the links to your other systems usually stay the same, and only the customer-facing screens need rebuilding for iPhone and Android.
There is also a middle option. Cross-platform tools such as React Native and Flutter let one codebase produce both an iPhone and an Android app. For most business apps this is cheaper than building two separate native apps, and the difference is rarely noticeable to customers. It is worth asking any developer which approach they plan to use and why.
The running costs people forget
The build is not the whole cost. Budget for these every year:
- Hosting and back-end services. Servers, databases, email and notification services. Often modest for a small business app, but it grows with users.
- Apple Developer Program. An annual fee (around £79 a year at the time of writing) to keep your app in the App Store.
- Google Play. A one-off registration fee.
- Updates. Apple and Google release new versions of iOS and Android every year, and apps need testing and updating to keep working and stay in the stores.
- Support and small changes. New features, fixes and content changes after launch.
A common rule of thumb is to set aside a percentage of the build cost each year for maintenance. The right figure depends on how much the app changes, so ask any developer for a written estimate of yearly running costs before you sign.
How to keep the cost down
- Write down the one job the app must do. Most first apps try to do too much. Launch with the core feature and add the rest once people are using it.
- Count your screens. A rough sketch of each screen on paper gives developers something concrete to price.
- Use what already exists. Payment providers, booking engines and login services save weeks of custom work.
- Start with a web app if the store is not essential.
- Ask for a fixed price, not an hourly estimate. Hourly quotes have a habit of growing.
- Get the ownership terms in writing. Code, store accounts and servers should be in your name.
Questions to ask before you sign
- Is this a native app, a web app or a cross-platform app, and why that choice?
- How many screens does the price include?
- Is the admin dashboard included?
- Who submits it to the App Store and Google Play, and is that in the price?
- What will hosting and maintenance cost each year?
- Who owns the code and the store accounts?
- What happens if I want to change developer later?
Our 12 questions to ask a web design agency covers more of the same ground.
Where an app fits with your website
For many businesses, the first step is not an app at all but a better website with online booking or ordering built in. If your customers come back often, such as a café, gym, salon or trade with repeat customers, an app can earn its keep. If they buy once a year, your website will usually do the job for less. It also helps to know how much a website costs so you can compare the two honestly.
If you have an app idea and want a fixed price, see our app development page or send us a short description of what it needs to do. Full packages are on our prices page.
Questions
How much does it cost to make an app in the UK?
A simple business app usually starts at around £5,000, an iPhone and Android app with customer accounts and payments at around £10,000, and a full platform with an admin dashboard at around £20,000 or more. Quotes vary widely between developers, so compare what each one includes.
Is a web app cheaper than an App Store app?
Yes, a web app is usually the cheapest way to give customers an app. It installs from your website onto any phone's home screen, needs no app store approval, and is built once for every device, which is why our web apps start at £4,995 compared with £9,995 for App Store and Google Play apps.
What are the yearly running costs of an app?
Plan for hosting and back-end services, app store fees and ongoing updates. Apple's developer programme has an annual fee and Google Play a one-off registration fee, and both stores expect apps to be updated for new phone software, so set aside a maintenance budget each year.
How long does it take to build an app?
A simple web app can be live in about 2 weeks, a native iPhone and Android app in about 4 weeks, and a full platform in 6 to 8 weeks with our packages. Time for app store review comes on top, and larger custom projects take longer.
Do I own the app once it is built?
You should, and it is worth getting that in writing. Ask for the source code, the app store listings and any server accounts to be in your business's name, so you are never locked in to one developer.