Guide · App costs
App development cost UK: what sets your quote, and how to ask for a fair one
On this page14 sections
In short: nobody can give you an honest pound figure for an app without a scope, and we do not publish an app price list. What we can show you is what the quote depends on. Eight decisions set it: which platforms you launch on, how much sits behind the app (the backend and admin panel), what it connects to, the personal data it holds, accessibility, store accounts, hosting, and support after launch. We settle these on a scoping call and then send a fixed written quote with milestones, so the full cost is known before work starts. Fees you pay to Apple, Google, payment providers or a cloud host go to them, not to us, and appear as separate lines. Use the tick-list below to see how big your first version is. If you only need the service itself, see our mobile app development page.
The eight drivers at a glance
| # | Driver | The decision | Why it moves the quote |
|---|---|---|---|
| 1 | Platforms | iPhone, Android, both, or a web app first | Each platform is a build, a test cycle and a store account |
| 2 | Backend and admin | Simple content, or accounts, orders and a staff panel | The part users never see is often the larger part of the work |
| 3 | Integrations | Payments, open banking, accounting, maps, messaging | Every outside service means its own rules, testing and failure cases |
| 4 | Personal data | What you collect, where it is stored, who can see it | Privacy notices, consent, deletion and access controls are build work |
| 5 | Accessibility | A stated target for who must be able to use it | Retrofitting is dearer than designing for it |
| 6 | Store accounts | Apple, Google, or both | Fees and review time paid to the store, not the developer |
| 7 | Hosting | Region, backups, a test environment | A monthly bill that grows with users |
| 8 | Support | Who fixes it after launch | Phones and stores change every year |
Why a single average app cost is the wrong number
Search for the cost of an app in the UK and you will find ranges that differ by a factor of dozens. They differ because the scope behind each is different: one supplier is pricing a form that saves to a database, another a two-sided marketplace. A fair comparison starts from your scope, not from a headline. If a supplier gives you a price in the first email, ask what it includes and what is out of scope. We prefer the opposite order: a short scoping call first, then a quote you can hold us to.
1. Platforms: one build or two
An iPhone app and an Android app are two builds with two test cycles, even when they share a code base. Launching on one platform and adding the other once the app has proved itself is a real way to stage the cost. Look at your own customers before you decide: a consumer app for the general public needs a different answer from a tool for your staff, who may all carry company phones. A web app that works in the phone browser is a third option for a first test, with no store review. We build mobile apps for iPhone and Android and agree the order with you on the scoping call.
2. The backend and admin panel behind the app
Most apps are a thin screen on top of a server. The server holds accounts, orders, content and rules, and your staff need an admin panel to see and change them. Owners often budget for the screens and forget the panel. Ask yourself who will refund an order, reset a password or approve a listing on day one. If the answer is "someone in the team", that person needs a screen, a login and permissions, and they are part of the scope.
3. Integrations: payments, open banking and the rest
Each connection to an outside service adds work, because the other side has its own rules, its own test environment and its own ways of failing. We integrate payment gateways such as Stripe, PayPal and Checkout.com as part of builds, and connect accounting tools such as Xero, Sage and QuickBooks through their official APIs. For payments, plan for the unhappy paths as well as the tap-and-pay path: a card that is declined, a payment that is pending, a refund, a customer who closes the app halfway. If you want to take payments directly from bank accounts (often called open banking), ask each supplier whether they connect through a regulated provider, since the app itself should not hold the customer's bank credentials. What a payment provider charges you per transaction is between you and the provider; read their price page before you decide, and keep it out of the build quote.
4. Personal data and UK GDPR
Almost every app collects personal data, even if only an email address. GOV.UK's guidance on data protection and your business says a business holding personal information must keep it secure, accurate and up to date, tell people who you are and how you will use their information, tell them they can see and correct their data and ask for its deletion, and respond when someone asks what you hold. It also mentions telling the Information Commissioner's Office how your business uses personal information. GOV.UK links to a separate page, "Pay the data protection fee", for that. We have not reproduced fee figures here: check the amount and whether it applies to you on the Information Commissioner's Office site.
For an app, those duties turn into specific work:
- A privacy notice shown at sign-up and inside the app.
- Consent screens where you rely on consent, with a way to withdraw it.
- A way to export a user's data and to delete their account.
- Role-based access so staff see only what they need.
- Logs, so you can tell what happened if something goes wrong.
- A choice of where the data is hosted, covered under hosting below.
If children may use the app, say so at the start: it changes the design. This is not legal advice. Have a UK data-protection adviser read the final scope.
5. Accessibility
The Equality Act 2010 requires UK service providers to make reasonable adjustments, as GOV.UK states. The detailed regulations on that same page, which require WCAG 2.2 AA and an accessibility statement for websites and mobile apps, apply to public sector bodies. If you are building for a council, a school, a charity or another public body, ask which rule applies to you. Private businesses are not named in those regulations, but a clear target such as WCAG 2.2 AA is still the simplest way to describe what you want in a quote. State it up front: sizing text, colour contrast and screen-reader labels are cheap to design in and expensive to fix after the screens are built.
6. App store accounts and fees
These are paid to the stores, not to a developer:
- Google Play. Google's help page states a US$25 one-time registration fee. New personal developer accounts need a closed test with at least 12 testers for at least 14 days before production, so build that time into your launch date. We read both pages on 12 November 2026.
- Apple. The Apple Developer Program is 99 US dollars per membership year, or in local currency where available. Apple's commission on digital goods sold through the App Store is 30%, or 15% under its Small Business Program, on that same page.
Open both accounts in your company's name, so the app stays yours if you change supplier. Check the current figures on the store pages before you budget, because stores change their fees.
7. Hosting and where the data lives
Hosting is a monthly bill that grows with users, storage and backups, and a separate test environment is what lets you release updates without breaking live users. We set it up on a major cloud provider in the region you need, such as the UK or EU, in an account in your company's name. The client owns the code, data and accounts, with a CSV export any time. Region matters for UK GDPR because it decides where personal data sits and who can reach it; choose it on purpose, and ask your adviser if you plan to send data outside the UK.
8. After launch: support is a separate line
Apple and Google ship a new operating system every year, and an app nobody maintains stops accepting even small fixes before long. Budget for support from day one: operating system and library updates, crash monitoring and small changes. It is quoted separately from the build. The backend and admin panel belong in the same plan; our custom software development page covers that side.
Pounds, VAT and how to structure the quote
We do not quote a pound price on this page. What you can control is how the agreement is built:
- Fixed scope, in writing. A feature list, the platforms, the integrations and what is out of scope. A fixed quote is only fixed if the scope is.
- Milestones, not one lump. Pay as each milestone is delivered and accepted.
- A named currency. Agree whether the quote is in pounds or another currency, and who carries any exchange-rate movement. Our team is based in India, so ask us which currency we are quoting in rather than assuming.
- VAT stated. Ask whether each figure includes VAT. GOV.UK gives the standard rate as 20% and sets the registration threshold at 90,000 pounds of taxable turnover. Whether VAT applies to a particular invoice depends on the supplier and on your status, so confirm it with your accountant.
- A change process. New features become written, priced change requests.
- Running costs listed separately. Hosting, messages, payment fees and store fees are billed by the provider.
Our quotes are fixed and written, after a scoping call, with currency and milestone dates agreed in the quote. The project starts once the scope and price are agreed.
Stage it: a first version that proves the idea
Most expensive apps are expensive because the first version tried to be the fifth. Keep the first release to the smallest thing a real user would use weekly. Anonymised, from our own work: for a container trucking company in the United States, we built the dispatch system the office runs on every day: a web admin panel, a back-end API and a driver app for iPhone and Android. The driver app records proof of delivery on the phone, a delivery photo and the customer's signature drawn on screen, and will not let a driver complete a delivery until both are captured. It shows how much of an app lives in the panel and the API, which is why we price all three together. See mobile app development for how we work, and the UK section for our other UK guides.
Tick what your app needs
Tap every item your first version needs. You get a rough size for the scope, one question to settle first, and a message you can send us. It is not a price.
Your ticks go into the message for you to read and edit. Nothing is sent until you press send in the form or in WhatsApp.
This runs in your browser. Nothing you tap is sent anywhere unless you choose to send it.
Published figures elsewhere differ in scope and change often; they are not our prices. Ask us for the price of your app below.
Price for your app
See the price for your app
Tell us what you need and we send you a price for your app and a fixed written quote after a short scoping call.
- Tell us what you need
- Short scoping call
- Price and fixed written quote
Items ticked above: 0. They are in the message below, ready for you to edit.
Prefer WhatsApp? Send the same request there.
Ask for the price on WhatsAppSources
- GOV.UK, Data protection and your business, VAT rates, Register for VAT and Accessibility requirements for public sector websites and apps. Opened 17 November 2026.
- Google Play Console Help, registration fee and testing requirements; Apple Developer, membership details. Opened 12 November 2026.
Where a source does not say something, we have not claimed it. We are not a law firm or an accountant: check the points above with a UK adviser before you rely on them.