App development cost is roughly: the screens and rules users see, plus the back end that stores and moves data, plus testing and store work, multiplied by whoever's hourly or daily rate you are paying. Then add the running cost of every year the app is live. Most confusing quotes come from leaving one of those pieces out.
The first piece, screens and rules, is what people picture: log in, browse, book, pay. The second is invisible: a database, an API, an admin panel for your staff, push notifications, emails, file storage. For many business apps the back end is as much work as the app itself. The third, testing and store submission, is what separates an app that ships from one stuck in review.
Rates are where UK and India differ most. UK agencies charge day rates that reflect UK salaries and overheads, and those rates vary a lot between London and the regions. A team in India charges less for the same hours. The formula does not change, only the multiplier.
- Front end: screens, flows, business rules
- Back end: database, API, admin panel, notifications
- Quality: testing on real devices, store submission
- Rate: who does the hours, and where
- Running: store fees, hosting, maintenance every year
App development cost UK by complexity tier
Grouping apps into three tiers gives a more honest picture than a single average. What moves an app up a tier is rarely the number of screens; it is payments, real-time data, multiple user types and integrations.
Tier 1: simple app
A single purpose, one type of user, content or forms, and a light back end. Think a members' information app, a loyalty card, or a field checklist that emails a PDF. With us this sits at our starting point of US$600, around six to eight weeks.
Tier 2: standard business app
Accounts, bookings or orders, card payments, push notifications, an admin panel for staff and one or two integrations. Most SME apps land here. With us, these are quoted above US$600, and at US$900 or more when the admin side becomes a web platform in its own right.
Tier 3: complex platform
Several user types (customers, staff, drivers), real-time tracking or chat, marketplace-style payments, offline sync and heavy integrations. Budget from US$900 with us, with the scope split into phases. Some tier 3 projects need more people than three developers can provide, and we say so upfront.
Not sure which tier your idea sits in? Describe it in a few lines and we will tell you, along with the features that push it up or down. The table of app types further down this page gives typical examples.
Why do UK agencies charge so much per hour for app development?
UK agency rates reflect UK salaries, office costs, account management, design teams and profit margin. Published guides put London agencies at the top of the range and regional agencies noticeably lower, but every agency sets its own rates, so quotes vary widely even for similar briefs.
What you get for that rate can be worth it: a project manager who chases decisions, designers who run user research, and people who can sit in your office. For a large programme with many stakeholders, that coordination saves money overall. For a focused business app with a clear scope, much of that coordination is overhead you pay for without needing.
When comparing, turn every quote into total cost for the same scope, not rate per hour. A cheaper hourly rate with twice the hours is not cheaper. Ask each supplier for an estimate broken down by feature, with the assumptions written next to each line.
If the agency question is the one you are wrestling with, our page on choosing a small remote team instead of a UK app company covers when each is the better fit.
What does it cost to build an app with a team in India?
With us, an Android and iOS app starts at US$600 and usually takes six to ten weeks for a first release; platforms with web portals start at US$900. The saving comes from labour costs in India, not from leaving out testing, back-end work or store submission.
You deal directly with the three people who build the app. One of us leads full-stack development, another of us handles cloud, data and AI features, and the third of us runs project management and automation. There is no account-manager layer between you and the code.
The trade-offs are real and worth naming. We work remotely and never visit. The overlap with UK hours runs from late morning, so live calls happen in your morning or around lunch. And three developers suit SME apps and MVPs, not programmes needing twenty engineers. If those limits are fine, the cost difference can be large.
Offshore is not always the right answer; our offshore vs local developers guide sets out when a UK team is worth the premium.
Native, Flutter or React Native: how the tech choice changes app cost
Building one cross-platform codebase for both iPhone and Android is usually the cheapest route for a business app, because most of the work is done once. Building two separate native apps (Swift for iOS, Kotlin for Android) roughly doubles the front-end effort.
We build in Flutter or React Native. Flutter draws its own interface and gives very consistent results across devices; React Native suits teams already working in JavaScript or TypeScript and can share logic with a web app. Both publish real apps to Google Play and the App Store, not wrapped websites.
Native still wins in specific cases: apps built around heavy 3D graphics, advanced camera processing, deep integration with watch or car platforms, or where an existing native codebase already exists. If your app is one of those, a cross-platform build may cost more in workarounds than it saves, and we will tell you so.
Choose Flutter when…
you want pixel-consistent design on both platforms, a custom look, and one team maintaining one codebase.
Choose React Native when…
you have JavaScript developers in-house, or a web app that should share code and logic with the mobile app.
Choose native when…
the app depends on platform-specific hardware features or high-end graphics that cross-platform tools handle poorly.
The back end: the app development cost nobody sees
Almost every business app needs a back end: somewhere to store accounts, bookings or orders, send notifications and give your staff an admin panel. It is often a third to half of the work, and it is the line most often missing from very cheap quotes.
There are two broad approaches. A managed backend service gives you authentication, a database and file storage with little custom code, which keeps the first release cheaper. A custom API on your own cloud account costs more to build but gives you full control of data, business rules and integrations, and avoids being tied to one vendor's pricing.
Either way, the admin panel deserves its own line in the quote. Your staff will use it every day to manage users, content, bookings and refunds. A clumsy admin side quietly costs hours each week. We build it as a simple web dashboard, which staff can use on a laptop without installing anything.
Hosting is billed monthly by the cloud provider straight to your card, not through us. For a small app it is modest; it grows with users, stored files and heavy features such as video. We estimate it during scoping so it is not a surprise.
Apple and Google developer accounts: what they cost and who should own them
Apple charges US$99 a year for the Apple Developer Program, and Google Play charges a one-time US$25 registration fee. Both accounts should be in your business's name, paid by you, because whoever holds the account controls the app's listing.
Apple's enrolment guidance says organisations need to be a legal entity, have a D-U-N-S Number, a work email on the organisation's domain and a public website. Getting a D-U-N-S Number can take time, so start this in week one. Google's Play Console Help says personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access; an organisation account avoids that step, and it is another reason to register properly.
On commission: Apple's App Store Small Business Program offers a reduced 15% commission on paid apps and in-app purchases for developers with up to 1 million USD in proceeds in the prior year. But Apple's guidelines (3.1.3(e)) say physical goods or services consumed outside the app, such as food, bookings or a class, must be paid with methods like Apple Pay or card entry rather than in-app purchase, so most business apps selling real-world services pay only normal card fees. Google revised its Play service fees for UK developers from 30 June 2026, so check the current Play Console Help page if you sell digital goods.
How much does app maintenance cost per year in the UK?
A common planning rule of thumb in the UK is to set aside around 15–20% of the build cost each year for maintenance. Treat it as a budgeting starting point rather than a law: a stable, simple app may need less, and an app with many integrations may need more.
Maintenance is not optional for an app in the way it can be for a small website, because the platforms move under you. Google Play's target API policy is a good example: from 31 August 2026, new apps and updates must target Android 16 (API level 36) or higher, according to Google's Play Console Help. Apple regularly raises the Xcode and SDK versions required for submissions too. An app nobody updates eventually cannot be updated at all without catch-up work.
Other recurring work: fixing crashes reported by real users, updating third-party libraries with security patches, adapting to new screen sizes, and small feature changes as your business evolves. With us, the first two months after launch are free. After that, a care plan starts at US$120/mo, covering updates, monitoring and small changes. Larger features are quoted separately before any work starts.
Fixed scope or time and materials: which is cheaper for a UK app?
A fixed-scope agreement is cheaper when you know exactly what the first release must do; time and materials is cheaper when the idea will change as you learn. The expensive mistake is choosing fixed scope for a vague idea, then paying for every change as a variation.
Under a fixed-scope agreement, the supplier prices an agreed list of features, often with milestones. You get budget certainty, but the supplier pads for risk, and anything outside the list becomes a change request. Under time and materials, you pay for the hours actually worked, usually against a weekly or monthly cap. You get flexibility, but you must manage priorities closely.
How we work: we send an itemised quote for an agreed scope, split into milestones, and nothing is billed before your written approval. If you want to add something mid-build, we price it first and you decide. For early-stage ideas we often suggest a smaller first milestone, a clickable prototype or MVP, so you learn before committing the bigger budget.
Fixed scope suits…
a clear brief, a firm budget, a funder or board that needs one figure, and a scope you are confident will not change much.
Time and materials suits…
a start-up still finding its product, ongoing development after launch, or work where research will reshape priorities.
Where cheap app quotes cut corners
A cheap quote is not a problem in itself; we are cheaper than UK agencies. The problem is a quote that is cheap because vital work is missing. These are the corners that usually get cut, and what each one costs you later.
- No back end or admin panel in the price, only the app screens
- Testing on one emulator instead of real iPhones and budget Android phones
- Store submission, screenshots and privacy labels left to you
- The app published under the developer's own store account
- Code in the developer's private repository with no handover
- Template or reskinned code sold as custom, with licensing unknowns
- No crash reporting or analytics, so you cannot see what breaks
- No plan for OS updates after launch
Ask any supplier to confirm each of these in writing. Apple's App Review Guidelines (4.2.6) also say apps created from a commercialised template or app generation service will be rejected unless submitted directly by the provider of the app's content, another reason your app belongs under your own developer account.
UK rules that affect app development cost: privacy, children and account deletion
Some requirements are fixed costs of doing it properly in the UK, and a quote that ignores them will cost more later. Build them into the first release rather than bolting them on after an App Store rejection or a complaint.
If your app handles personal data, UK GDPR applies: a clear privacy notice, a lawful basis for each use of data, security, and the ability to respond to access and deletion requests. If the app is likely to be used by children, the ICO's Children's code sets out fifteen standards for online services such as apps and games, which affects defaults, data collection and design.
Apple adds its own rule: guideline 5.1.1(v) says that if your app supports account creation, it must also offer account deletion within the app, and Apple's guidance says deactivating an account is not enough. That means real back-end work to delete data, which a cheap quote often omits. We build these pieces in and design data flows with minimisation in mind. Legal sign-off on your privacy notice and data practices belongs with your own solicitor.
How to reduce app development cost without cutting quality
Cut scope, not quality. The cheapest reliable app is the one that does fewer things well at launch, then grows based on what real users do.
- Launch with the one journey that makes money or saves time; park the rest
- Use a managed backend or existing services (payments, maps, email) instead of custom builds
- Start with a cross-platform codebase, not two native apps
- Supply your own text, images and brand assets
- Make decisions quickly: waiting time costs money on any contract
- Link to an existing booking or shop system before rebuilding it
- Consider a web app first if users will not install anything
For many service businesses, a fast mobile website does the job at a fraction of the price; our guide to how much a website costs in the UK shows those numbers. A web app can also be a sensible first step before a store app.
Do you actually need an app, or would a website do?
You need an app when people will use it repeatedly and benefit from being on their home screen: push notifications, offline access, camera or location features, saved details, fast re-ordering. If most visitors come once, a website is cheaper and reaches more people.
A useful test: will a typical user open this more than once a week? A gym member booking classes, a driver checking jobs, a regular re-ordering a takeaway: yes, an app earns its keep. A customer checking your opening hours or reading about your services once: no, a good website is enough.
Plenty of businesses start with a website and add an app once the demand is proven. Our takeaway online ordering page shows that approach: website first, app when regulars justify it. The same logic applies to clinics, salons and gyms.
Building an app with a team in India from the UK: overlap, testing, payment and the first two weeks
Most of the collaboration happens asynchronously, which suits app work well. You send feedback at the end of your day; the fix is often waiting on your phone as a new test build when you start the next morning. India is four and a half hours ahead of the UK in summer and five and a half in winter, and the working overlap runs from your late morning.
Test builds reach you through Apple's TestFlight and a Google Play testing track, so you try the real app on your own phone throughout the project. Calls happen on Zoom, Meet, Teams or WhatsApp. We quote in USD and invoice from India; UK clients usually pay from a GBP account through Wise, bank wire or PayPal, in milestones set out in the written quote.
Week 1
Call to walk through your idea, written list of user types and journeys, and an itemised quote in about two working days. You start Apple and Google developer enrolment in your business name.
Week 2
Clickable screen designs for the main journeys, reviewed on a video call. You create the code repository and cloud account in your name and invite us. The first milestone begins once designs are signed off.
There are no site visits and no local office; everything runs online. If the remote model is new to you, hiring developers in India explains how it works in more depth.
Worked example: costing a hypothetical driving-school app in Nottingham
Picture a hypothetical driving school in Nottingham with eight instructors. It wants pupils to book and pay for lessons in an app, instructors to see their day and mark lessons complete, and the office to manage everything from a laptop. This is an illustration of how we would price it, not a client project.
Scope: a pupil app (sign up, book, pay by card, reminders, lesson history), an instructor view inside the same app with a different role, and a web admin panel for the office. That is three user types plus payments and notifications, firmly tier 2, edging into tier 3 because of the admin platform. Account deletion is built in from the start.
Estimate: because the web admin is substantial, this is quoted from US$900, around ten to twelve weeks, split into milestones: designs, pupil booking and payments, instructor features, admin panel, testing and store release. Running costs, billed to the school: Apple US$99 a year, Google Play US$25 once, cloud hosting monthly, card processing fees per lesson. Maintenance free for two months, then from US$120/mo.
A cheaper first phase would drop the instructor features and let the office manage diaries in the admin panel, bringing the app nearer our US$600 starting point, with phase two added once pupils use it.
App budget checklist before you ask anyone for a quote
Answer these before contacting any developer. Suppliers can only give comparable prices when they are quoting the same thing, and these answers are what makes the app development cost predictable.
- Who are the user types (customers, staff, admins)?
- What is the one journey that must work at launch?
- Do users pay in the app, and for physical or digital things?
- Which existing systems must it talk to?
- Does it need to work offline, use location or the camera?
- Who will manage content and users day to day?
- Is the app likely to be used by children?
- What is the budget for year one, including running costs?
- Are your Apple and Google accounts registered in your business name?
- What will you measure to decide whether phase two is worth it?
Send the answers to us on WhatsApp or through the contact page and you will get an itemised quote, with each assumption written down.