Development

App maintenance cost in the UK: what you pay after launch, and why

What an iOS or Android app costs to keep running after launch: the yearly store requirements, hosting and third-party bills, UK retainer and hourly ranges, a worked example for three apps and what a maintenance agreement should say.

By the WE-DEV teamPublished 12 min read
Close-up of a precision screwdriver bit set in a black leather roll on a workbench, the kind of small tools used for regular upkeep, representing ongoing app maintenance

App maintenance cost in the UK usually works out at roughly 15 to 20 % of the original build cost per year. That is a rule of thumb, not a tariff, and in our experience it is a fair starting point (some UK agencies quote 15 to 25 %): an app that cost £15,000 to build needs about £2,250 to £3,000 a year, and one that cost £45,000 needs about £6,750 to £9,000. On top of that come the running costs you pay to other companies: store fees, hosting, and usage-based services such as SMS and maps. All figures here exclude VAT.

The money goes on keeping the app working as iOS and Android change underneath it, fixing what real users break, and keeping the store listings alive. Very little of it is optional.

What app maintenance covers

“Maintenance” sounds like a vague retainer for doing nothing much. In practice it is seven fairly specific jobs.

Yearly OS releases and the store rules that follow

Apple and Google each ship a major operating system version every year. New versions change permission prompts, background limits, notification behaviour and screen sizes, and something in your app will usually need adjusting. Even if nothing visibly breaks, the stores set deadlines of their own.

  • Google Play. Under the target API level policy described in Play Console Help, new apps and updates must target an Android version released within about the last year. Existing apps that fall more than about two years behind stop being available to new users whose phones run a newer Android version than the app targets. People who already installed it can keep using it. The required level moves up every year, with the deadline usually falling in late summer.
  • Apple. Apple Developer announces each year a minimum Xcode and SDK version that every upload to App Store Connect must be built with, typically taking effect in the spring. An app built two years ago still runs, but you cannot ship so much as a typo fix until the project has been brought up to the current tools.

The exact versions change annually, so check the current pages before planning work. In practice an app cannot simply be left alone: after a year or two you lose the ability to update it, and on Android you start losing new users.

Dependency and SDK updates

In the apps we maintain, we typically find somewhere between 20 and 60 third-party packages once you count everything the project pulls in: payments, analytics, maps, sign-in, image handling, push messaging. Each has its own release cycle. Payment and sign-in SDKs in particular retire old versions on a schedule, and the stores add policy requirements through them. Recent examples include privacy declarations for the data an app and its SDKs collect, and the rule on both stores that an app which lets people create an account must also let them delete it.

Updating little and often is cheap. Updating everything at once after two years is where the unpleasant quotes come from, because one package needs a newer version of another, which needs a newer build system, and so on down the chain.

Bug fixes and crash monitoring

Testers use a dozen devices. Your customers use hundreds, some of them six years old with a cracked screen and 200 MB of free storage. A crash reporting tool (Firebase Crashlytics and Sentry are the common ones) shows which crashes affect the most people, so the hours go on the faults that matter. Somebody has to look at that dashboard, though. A monitoring tool nobody reads is the most common gap we find when we take over an app.

Backend hosting and third-party services

The app on the phone is half the system. The other half is the server or cloud service behind it, and that has monthly bills.

  • Hosting. A small app on Firebase or a modest server often costs from nothing to about £50 a month. A busy app with a custom back end, database backups and a staging copy is more often £100 to £500 a month, and marketplaces can go well beyond that.
  • Push notifications. Sending through Apple’s and Google’s own services is free, and Firebase lists Cloud Messaging as a no-cost product. Marketing platforms that sit on top, with segmentation and scheduling, charge by audience size.
  • Maps and location. Google Maps Platform is priced by usage with a free monthly allowance. A store locator rarely leaves it. Live driver tracking can.
  • SMS. Text messages to UK numbers cost a few pence each through the usual providers. At around 4p a message, 5,000 verification texts a month is roughly £200, which is why we usually suggest email or push for anything that is not a security code.
  • Payment fees. Card processors charge a percentage plus a fixed fee per transaction. The rate depends on the card type and the provider, so check their current UK pricing page.

Store fees and commission

The Apple Developer Program costs US$99 a year, charged in local currency, according to Apple Developer. If the membership lapses, the app comes off the App Store. Google Play charges a one-off US$25 registration fee.

Commission only applies if you sell digital goods or subscriptions inside the app. Apple’s standard rate is 30 %, and its App Store Small Business Program cuts that to 15 % for developers earning up to US$1 million a year. Google Play changed its fees for UK users on 30 June 2026. According to Play Console Help, it now charges a 10 % service fee plus a 5 % billing fee on a developer’s first US$1 million of earnings each year and on auto-renewing subscriptions. Above that, other purchases are charged 20 % plus the 5 % billing fee for new installs and 25 % plus 5 % for people who installed the app before that date. The terms keep shifting. In summer 2026 the Competition and Markets Authority consulted on requiring Apple and Google to let UK developers point customers to payment options outside the app, and Apple has already changed its fees in the EU. Confirm the current terms before building a business model on them. Physical goods and real-world services, such as a haircut or a car wash, are normally paid for through a card processor and are not subject to store commission.

Security patches

Vulnerabilities turn up in server software, frameworks and packages all the time. If your app holds personal data, UK GDPR expects “appropriate technical and organisational measures” to protect it, and keeping software patched is one of the most basic of those measures. On the app side, that also means renewing signing certificates and keys before they expire. Apple distribution certificates expire and have to be renewed, and a lapsed one stops releases at exactly the moment you need to push a fix.

Small improvements

The last slice is the part you get to choose: a clearer booking screen, a new filter, a report your staff keep asking for. A sensible maintenance budget leaves room for a few of these each quarter.

The maintenance calendar

The work is predictable enough to plan. This is the pattern of recent years; dates move, so treat it as a guide.

WhenWhat happensWhat your developer does
SpringApple’s new minimum Xcode and SDK requirement usually takes effectRebuild with current tools, fix warnings, release
JuneApple previews the next iOS; betas startRun the app on the beta and list what breaks
Late summerGoogle Play’s target API level deadlineRaise the target level, retest permissions and background behaviour, release
AutumnNew iOS reaches the public, on new phone modelsRelease the compatibility update, ideally in the same week
All yearAndroid releases, SDK updates, security advisories, crashesMonthly dependency updates and a look at the crash dashboard
AnnuallyApple membership, certificates, domains and API keys renewRenew early and record the dates somewhere shared

App maintenance cost: UK price ranges

There are two ways the work is normally sold. The ranges below are what we see in UK quotes, not a survey.

  • Monthly retainer. Roughly £300 to £800 a month for a simple app, £800 to £2,500 for an app with accounts, payments and a custom back end, and £2,500 to £8,000 or more for a marketplace or on-demand platform with several user types. Retainers come out higher than the 15 to 20 % rule because they also pay for monitoring and a guaranteed response time, not only for the hours worked.
  • Pay-as-you-go hours. UK agencies mostly charge somewhere between £50 and £120 an hour for mobile work, often with a minimum booking. Our own Mobile Application rate is £70 an hour.

The rule of thumb of 15 to 20 % of the build cost per year is a fair starting point for the labour. It runs higher in year one, when real users find what testing missed, and for apps with two separate native codebases. It runs lower for a simple app that changes little.

Worked example: three apps

These three are illustrative, with build costs taken from typical UK agency ranges. The running costs column is money paid to third parties, not to your developer.

ItemSimple content or booking appApp with accounts and paymentsMarketplace or on-demand app
Example build cost£15,000£45,000£120,000
Maintenance at 15–20 % a year£2,250–£3,000£6,750–£9,000£18,000–£24,000
Equivalent per month£190–£250£560–£750£1,500–£2,000
Rough hours at £70/h32–43 a year96–129 a year257–343 a year
Third-party running costs£300–£1,200 a year£1,500–£6,000 a year£6,000–£25,000+ a year
What moves the figureHow often content and opening rules changeNumber of integrations; card and identity SDK changesLive tracking, SMS volume, support for two or three user apps

To make the first column concrete at our rates: 50 hours of Mobile Application time is £3,500, less the 20 % volume discount for a 50-hour block, which comes to £2,800. Add VAT of £560 and the total is £3,360. Hours bought through our hourly hire page never expire, so a block like that would typically see a simple Flutter app through a year of updates with some left for improvements. If you are still at the budgeting stage, our guide to how much an app costs to build has the build side of the sum.

Retainer, ad-hoc hours or in-house

ItemMonthly retainerAd-hoc or pre-paid hoursIn-house developer
Typical costFixed monthly feeHourly rate; only what you useSalary plus National Insurance, pension, equipment and management time
Response to an urgent faultAgreed in writingBest effort unless agreedImmediate, when they are not on holiday
Who watches for store deadlinesThe supplierYou, unless you askYour developer
RiskPaying for quiet monthsNobody is looking between jobsOne person holds all the knowledge
SuitsApps that take payments or run daily operationsSimple apps with a predictable yearly cycleApps that are the product, with constant feature work

Our view: if the app takes money or your staff cannot work without it, pay for a retainer with a response time attached. If it is a content or simple booking app, pre-paid hours plus a diary reminder for the two store deadlines is usually enough. Hiring in-house rarely makes sense for maintenance alone, since one mobile developer costs more than the whole maintenance budget of most business apps. It starts to make sense once you have enough new feature work to fill their week.

Whichever route you choose, the same question applies to who does the work. Our comparison of a freelance developer and an agency covers cover for holidays and illness, which matters more for maintenance than for a one-off build.

How Flutter and other cross-platform frameworks change the bill

With separate native apps, every fix is written twice, by people with different skills, and tested twice. A cross-platform framework such as Flutter or React Native keeps one codebase for both platforms, so a bug in the booking flow is fixed once and released to both stores. For a typical business app that removes a large share of the duplicated effort, and it is the main reason we build most apps in Flutter through our mobile app development service.

It does not halve the bill. What stays the same:

  • Two stores, two rulebooks. Both deadlines, both review processes and both sets of privacy forms still apply.
  • Native tooling underneath. A Flutter project still contains an Xcode project and an Android build configuration, and both need updating each year.
  • The framework is one more dependency. Flutter ships several stable releases a year, and now and then one needs code changes.
  • Plugins that wrap native SDKs. Payments, maps and Bluetooth packages depend on their maintainers keeping up. An abandoned plugin has to be replaced or taken over.
  • Platform-specific features. Home screen widgets, watch apps and deep system integrations are written natively whatever the framework.
  • The back end. Servers, databases and third-party bills are unaffected.

What happens if you do nothing for two years

Nothing dramatic happens on day one, which is why maintenance gets cut. The decline is gradual and follows a familiar order.

  1. Months 1 to 6. Small bugs on new phones go unfixed. Ratings drift down.
  2. Around month 12. A new OS version changes something, perhaps notifications or photo access. You can no longer upload an update to either store without first bringing the project up to date, so a ten-minute fix becomes a multi-day job.
  3. Months 12 to 24. A third-party service retires the version of the API your app calls. A feature stops working with no change on your side.
  4. Around month 24. On Google Play, the app falls outside the target API window and is no longer offered to new users on recent Android versions. Apple’s own clean-up comes later: under its App Store Improvements process, an app that has not been updated for three years and has had almost no downloads in the past twelve months gets 90 days’ notice to submit an update before it is removed.
  5. Throughout. Known security holes in old packages and server software stay open.

Recovering from that state is nearly always possible. It typically costs more than the maintenance that was skipped, because the upgrades have to be done in sequence and each step needs a full retest. Our software testing checklist shows what a proper regression pass involves.

What a maintenance agreement should say

Most disputes about maintenance come from an agreement that says “support and maintenance” and nothing else. Before signing, check that it answers these points.

  • What is included: OS compatibility updates, store compliance work, dependency updates, monitoring, server patching, and whether small improvements count.
  • What is not included and how it is priced: new features, redesigns, third-party fees.
  • Response and fix times by severity, with hours of cover. “App will not open” and “wrong shade of blue” need different clocks.
  • Monthly hours and whether unused hours roll over or expire.
  • Reporting: a short monthly note of what was updated, crash-free rate and anything coming up.
  • Store accounts in your name. The Apple Developer and Google Play accounts should belong to your company, with the supplier added as a user. Moving an app out of an agency’s account later is possible but slow.
  • Code ownership and access. You own the source code and have access to the repository at all times, not on request.
  • Credentials: signing keys, certificates, API keys and server logins held in a password manager you control.
  • Backups and recovery: how often the database is backed up and how long a restore takes.
  • Handover: on termination, documentation, a working build and a fixed number of hours to brief the next developer.
  • Notice period and price reviews. One to three months’ notice is normal.

If you are commissioning a new app, ask for the first year of maintenance to be priced in the same quote as the build. It is the simplest way to compare suppliers on the real cost of ownership.

We are based in London and maintain apps for businesses across the UK, including apps we did not build. If you have inherited one and are not sure what state it is in, get in touch and we will review the code, the store accounts and the bills, and tell you what a year of maintenance should cost.

Frequently asked questions

How much does app maintenance cost per year in the UK?

A common rule of thumb is 15 to 20 % of the original build cost per year for the development work, so about £2,250 to £3,000 for a £15,000 app. Hosting, store fees and usage-based services such as SMS are extra and range from a few hundred pounds a year for a simple app to £25,000 or more for a busy marketplace.

Do I have to update my app every year?

In practice, yes. Google Play requires apps to target a recent Android API level and stops offering out-of-date apps to new users on newer Android versions. Apple requires every upload to be built with a recent Xcode and SDK. The required versions move up each year, so check Play Console Help and Apple Developer for the current ones.

What are the App Store and Google Play fees?

The Apple Developer Program costs US$99 a year and Google Play charges a one-off US$25 registration fee. If you sell digital goods or subscriptions in the app, the stores take a commission. Apple charges 30 % as standard and 15 % under its Small Business Program. Since 30 June 2026 Google Play has charged UK developers a 10 % service fee plus a 5 % billing fee on their first US$1 million a year and on subscriptions, and 20 to 25 % plus the billing fee on other purchases above that. Check current terms, as the Competition and Markets Authority has been consulting on further changes.

Is a Flutter app cheaper to maintain than two native apps?

Usually, because most fixes and updates are made once in a single codebase. You still have two stores with their own deadlines and reviews, native build settings to keep current and the same back end and third-party costs, so the saving is real but well short of half the total bill.

Can another company maintain an app it did not build?

Yes, provided you have the source code, the signing keys and access to the store accounts. Expect the new supplier to charge for an initial review, typically a few days, to get the project building and to list what is out of date before quoting for ongoing work.

Is a monthly retainer better than paying by the hour?

A retainer suits apps that take payments or run daily operations, because it comes with agreed response times and someone watching for store deadlines. Pre-paid or ad-hoc hours suit simple apps with a predictable yearly cycle, as long as somebody on your side keeps track of those deadlines.

WE-DEVUK software and web development agency. We build websites, custom software, mobile apps and online shops, and write these guides from the projects we run every week.

Photo: Mika Baumeister via Unsplash

Read next

Ready when you are

Tell us what the business needs.

A developer replies within one working day. Fixed price or hourly, your choice — and the code is yours.