# App maintenance and support UK: monthly plans with written terms

Canonical: https://appagentix.co.uk/services/maintenance-support/

Our app maintenance and support keeps live iPhone, Android and web apps working, on written terms you can check.

- Monthly plans with written reply times and exclusions
- App takeover from another team, with an audit report in 10 working days
- Fixed for 3 months, then 30 days’ notice; code and accounts in your name

## How much does it cost to maintain an app?

Plans cost from £750 a month excluding VAT, for 8, 18 or 32 engineering hours, with a written reply clock. On Standard, a gym group’s class booking app comes to £18,600 in year one with hosting, before store fees. Price your own version with the calculator on this page.

- Critical-fault clock: from your written report, 4 working hours on Essential and 2 on Standard and Premium

## What is mobile app maintenance?

### System updates

Your app runs on each new Apple and Google version from the summer test releases, so fixes are ready early. Android 16 had 44.27% of UK Android browsing in October 2026 (StatCounter, October 2026).

### Crash watching

Each week we rank the Firebase Crashlytics or Sentry crash list by users affected, and plan hours go to the top; the report shows the crash-free rate.

### Security patches

Libraries with an advisory are updated, and keys and certificates are renewed before they expire. Only 34% of UK businesses have a policy to apply software security updates within 14 days (DSIT Cyber Security Breaches Survey 2025/2026).

### Store releases

We test each build on a written device list, write release notes, answer reviewers and resubmit after a rejection.

## The monthly support loop

What happens every month after launch.

1. Watch crashes
2. Fix
3. Update OS and libraries
4. Security patches
5. Monthly report

## App maintenance and support plans, with reply clocks

We look after 20 to 40 live apps at any time. Each plan covers one app on both phones, or one web app.

| Option | Price | Time | Includes |
| --- | --- | --- | --- |
| Essential | 8 hours a month | Reply clock: 4 working hours | Weekly crash review, compatibility checks, security patches, a store release a quarter and the monthly report. |
| Standard | 18 hours a month | Reply clock: 2 working hours. Fix clock: 1 working day target | All of Essential, a monthly release, a named engineer and a quarterly restore test. |
| Premium | 32 hours a month | Same clocks as Standard | All of Standard, a 10-device test run per release, a WCAG 2.2 AA re-check of changed screens and a monthly planning call. |
| Takeover audit | One-off | Report in 10 working days | Code, libraries, crash history and store listings, with keep, fix and rebuild lists in hours; credited against month one. |
| Extra hours and features | Hourly | Quoted before work starts | Beyond the monthly hours: a feature is quoted as a fixed figure, and an AI agent on one workflow is a separate project. Unused hours carry over one month. |

## Estimate your support plan in a minute

Pick a plan, extra hours and a starting point to see a total for the 3-month minimum.

Essential for the 3-month minimum, at £750 a month: £2,500 to £2,500, 12 to 13 weeks.

### Plan

- Essential, £750 a month, 8 hours: included
- Standard, £1,400 a month, 18 hours: £2,000 to £2,000
- Premium, £2,400 a month, 32 hours: £5,000 to £5,000

### One-off extra hours at £90

- None: included
- 10 hours (£900): £1,000 to £1,000
- 20 hours (£1,800): £2,000 to £2,000
- 40 hours (£3,600): £3,500 to £3,500

### Starting point

- Our own app, no audit: included
- Takeover of another team’s app: £1,000 to £2,000

An estimate, not a quote, excluding VAT, as of November 2026, with totals rounded to the nearest £500. Later months cost the plan price until 30 days’ notice; the audit fee is credited against month one.

## When the reply and fix clock runs

**Reply and fix clock**

| Event | Who acts | Clock |
| --- | --- | --- |
| Critical-fault report arrives in writing | You | Both clocks start, or at the next working hour. |
| Fault confirmed, next step named | Us | Reply clock stops: 4 working hours on Essential, 2 on Standard and Premium. |
| Login, test account or decision needed | You | Fix clock pauses until it arrives. |
| Fix live, or sent to the store | Us | Fix clock stops: 1 working day target on Standard and Premium. |
| Apple or Google review | Store | Not counted. |
| Fault shows only on a beta | Us | Starts at the public release. |
| New iOS or Android version goes public | Us | Written result within 10 working days. |
| Critical library advisory | Us | Patched or mitigated within 5 working days. |
| Notice given | Either side | 30 days to the end; our access removed within 1 working day after. |

Working hours run Monday to Friday, UK time, not bank holidays. A critical fault means the app will not open, or sign-in or payments fail; Essential has a reply clock only.

## What we need from you, and when

Each wait on these items pauses the fix clock, so we ask for each before the work that needs it.

- **Named-user logins.** Code, cloud and crash tool accounts, before month one starts or in days 1 to 3 of a takeover.
- **Store access.** App Store Connect and Google Play Console roles, before the first store release.
- **A decision-maker.** One named person who approves quotes and out-of-hours releases, from month one.
- **Test accounts.** One sign-in for each type of user, ready before we test the first release.

## The monthly app maintenance report, filled in

The gym app’s third month on Standard, with one fault still open.

**Monthly maintenance report, October 2026**

| Check | Result | Note |
| --- | --- | --- |
| Crash-free sessions | 99.6% | Last month 99.3%. |
| iOS 27 on iPhone 15 and iPhone 16e | Pass after fix | Profile photo upload failed; fixed in build 2.6.1, live on 9 October. |
| Security advisories | Pass | One critical advisory on the image library, patched in 3 working days. |
| Backup restore test | Pass | Database restored to a test server in 42 minutes. |
| AI help assistant, 60-case test set | 55 of 60 | Last month 57 of 60: 92 percent against 95, under the 5-point trigger. |
| Android class reminders arriving late | Open | Seen on Galaxy A15 in battery saver mode; fix due in build 2.6.2, retest on Pixel 8. |
| Engineering hours | 14 of 18 used | The 4 unused hours carry over to November only. |

An example for an imaginary app, not a client result.

## What our app support services do not cover

- **New features.** New screens or payment methods are quoted first; they use plan hours only if you ask.
- **Third-party bills.** Apple and Google store fees, hosting, maps, SMS and email bill your own accounts.
- **Provider outages.** A failing payment, map or sign-in provider is reported, with a workaround where possible.
- **Out-of-hours work.** No plan covers evenings, weekends or bank holidays; planned out-of-hours releases are quoted first.
- **Beta-only faults.** We test on betas to prepare, but the clock starts at the public release.
- **Content entry.** Text, prices and images in your admin panel are yours to enter; we fix the panel.
- **Hardware.** We test on our written device list but do not supply or repair devices.
- **Formal sign-off.** Premium re-checks changed screens; formal accessibility audits and legal advice need a specialist.
- **Zero crashes.** No one can honestly promise that: you get reply times and a crash-free figure, not an uptime percentage.

## How we take over an app another team built

The National Cyber Security Centre dealt with 204 nationally significant cyber attacks in the 12 months to August 2025. An inherited app gets a security scan in its first two weeks.

### Get access (Days 1 to 3)

You add us as a named user to the code, store, cloud and crash tool accounts; we never ask for a password.

You receive: A list of every system and who owns each login.

### Read and run the code (Days 2 to 7)

We build the app from source on a clean machine; a failed build is the first finding.

You receive: A confirmed build, or an exact list of blockers.

### Audit (Weeks 1 to 2)

We scan libraries for advisories, read 90 days of crash history, check store listings and test on real devices.

You receive: The written audit: keep, fix and rebuild lists with hours.

### Stabilise (Weeks 2 to 4)

We fix the worst faults, update what is dangerously old and set up monitoring you can open.

You receive: A release in the stores and a first crash-free rate.

## A takeover audit report, filled in

The same gym app three months earlier: each row ends in keep, fix or rebuild, with hours. We have been building apps since 2019.

**Takeover audit, class booking app, July 2026**

| Area | Finding | Verdict | Hours |
| --- | --- | --- | --- |
| Build from source | Would not build: one private package was missing | First finding, fixed on day 5 | 6 |
| Payment library | Abandoned since 2023 | Fix: replace it | 14 |
| Booking calendar | Crashes on iPhone SE (3rd gen), 41% of all crashes | Fix | 9 |
| Database backups | Nightly backups, restore never tested | Fix: run a restore test | 4 |
| Store listings | Privacy answers out of date in both stores | Fix | 3 |
| Sign-in and accounts | Works and is covered by tests | Keep | 0 |
| Staff admin panel | Framework version no longer gets security updates | Rebuild, quoted separately | 60 |
| Android signing key | Held by the previous developer | Open: you request it in writing, and we check again on day 10 | Not known yet |

Fix list: 6 + 14 + 9 + 4 + 3 = 36 hours. Crash history adds a forecast 54 hours, so the year of repairs comes to 90 hours, set against a full rebuild quote. This is an imaginary app, not a client result.

## Repair, refactor or rebuild: how we decide

Our longest client relationship is seven years and counting. We earn more from repairs, so our rule is written down: repairs mean a year of fault-fixing hours, not routine upkeep.

What does a year of repairs cost against a rebuild quote?

- If a year of repairs costs under 40 percent of the rebuild quote, choose **Keep repairing**. Plan hours cover it: in the audit above, 90 hours of repairs come to 15 percent of the rebuild quote.
- If repairs cost 40 to 50 percent of the rebuild, with faults in a few named parts, choose **Refactor in stages**. Those parts are replaced one at a time as quoted work: for this app, 240 to 300 hours.
- If repairs cost over half of the rebuild, or the app will not build and its libraries are abandoned, choose **Rebuild**. A new fixed-price project, with an MVP-sized app built in 8 to 14 weeks.

## Who owns the code, the accounts and the data

### Your code

Yours from day one, in a repository your organisation owns, with a full copy within 2 working days of asking.

### Your accounts

In your company’s name, with us as users on the lowest rights the work needs, removed within 1 working day of the end.

### Notice period on an app maintenance contract

Months one to three pay for set-up; then either side ends it with 30 days’ notice, no exit fee and a hand-over document.

### Launch fixes

On apps we built, fixes are in the build price for 3 months (90 days); a plan adds the upkeep.

### Personal data

You are the controller and we are your processor, under an agreement signed before we see live data, which never goes on laptops.

## What is a maintenance service contract?

A maintenance agreement sets what a month buys, how fast we reply and how you leave.

**Agreement summary, class booking app, Standard plan**

| Term | What it says |
| --- | --- |
| Covers | One app on both phones: crash review, updates, patches, a monthly release, the report. |
| Excludes | Features beyond the hours, store and cloud bills, provider outages, out-of-hours work, content entry, devices. |
| Price and hours | A fixed monthly fee for 18 hours; extra hours quoted first; unused hours carry one month. |
| Reply and fix clock | 2 working hours to reply, 1 working day fix target, from your written report. |
| Term and notice | Months 1 to 3 fixed, then 30 days’ notice either side, no exit fee. |
| Ownership | Code in your repository; store and cloud accounts in your company’s name. |
| Data protection | You are controller, we are processor; a data processing agreement before live data. |
| Exit | Hand-over document in the last month; repository copy in 2 working days; access removed in 1. |
| Out-of-hours release | Open: a Sunday release for the January timetable, quoted before booking. |

An example for an imaginary app, not a client result.

## If your app contains AI, how we check it

A provider can update its model, so answers right in March can change by June. In September 2026, 30% of UK businesses reported using at least one type of AI technology (ONS Business Insights and Conditions Survey).

1. **Test set.** 30 to 100 real questions or documents, with the answers you accepted at launch.
2. **Monthly run.** The same set is rerun on the live feature each month.
3. **Compare.** The pass rate sits beside last month’s in your monthly report.
4. **Review trigger.** A drop of more than 5 points starts a review.
5. **Cost line.** The month’s AI running cost goes in the same report.

The last step feeds the first: the loop repeats.

## UK rules that shape app maintenance

A reportable personal data breach must reach the Information Commissioner’s Office within 72 hours of your becoming aware of it, where feasible. As your processor we tell you without undue delay, but the report is yours, so the app needs logs of what happened.

Section 29 of the Equality Act 2010 bars any business serving the public from discriminating against people who need its service, and public sector apps must meet WCAG 2.2 AA. Premium re-checks every changed screen; other plans flag new screens that fall short.

## Apps we have built that people use every day

A few examples from the many apps we have built that are live in the stores and in daily use by patients and drivers.

### MyUTHealth: a patient app in daily use

Healthcare

We built MyUTHealth, the Android app patients use to request visits, read results, order repeat medicines and contact their care team. It sits on Epic MyChart through HL7 FHIR APIs, so each release has to keep that link, encrypted traffic and push reminders working, and we test it with JUnit in Android Studio.

Rated 4.4 stars by more than 750 reviewers, with 50,000+ Google Play downloads

[Read the MyUTHealth case study](https://appagentix.co.uk/our-work/myuthealth/)

### Tiger Charge: an app drivers rely on at the charger

EV charging

We built Tiger Charge, the Android app drivers use to find, start, follow and pay for a charge, linked over OCPP to the chargers themselves. It holds a prepaid wallet, session history, invoices and alerts on the phone, by text and by email, and runs on Node.js, PostgreSQL and Redis on AWS.

4.1 stars on Google Play from the drivers who use it

[Read the Tiger Charge case study](https://appagentix.co.uk/our-work/tiger-charge/)

## When another route is the better choice

### The app is under six months old and still changing

That needs a development team, not a fixed-hours plan, until the screens and features settle.

### You need a fix once or twice a year

A monthly plan is poor value: book the takeover audit, then buy hours when you need them.

### The app must be answered at night

Our reply times run in UK working hours; a 3am reply needs a staffed 24-hour desk.

## Questions about app maintenance and support

### How much does it cost to maintain an app?

Essential starts at £750 a month, excluding VAT, with Standard and Premium adding hours and faster clocks. On the gym app above, plans run 15 to 48 percent of the build each year, against the 15 to 25 percent agency guides quote.

### How much does app development and maintenance cost?

A first version costs £15,000 to £40,000, excluding VAT, and a full iPhone and Android app costs more. Fixes are included for 3 months after launch, then a monthly plan takes over. Our app development cost page lists every price.

### What will happen if I don't update my apps?

A new Apple or Google version can break features, as in our sample report where profile photo upload failed on iOS 27. Our plans also update libraries with a security advisory and renew keys and certificates before they expire. Our plans test each new iOS and Android release and send a written result within 10 working days.

### What should be included in a maintenance agreement?

The monthly price and hours, the reply and fix clock and what is not covered. Then the minimum term and notice, who owns the code and accounts, data protection and hand-over, as filled in above.

### What is the purpose of a maintenance agreement?

It puts in writing what a monthly fee buys: the hours, the reply clock, what is not covered, the term and notice, and who owns the code. Both sides then know what to expect and how to leave.

### How to write up a maintenance contract?

Start from numbers, not adjectives: the price, the hours, each reply time and the minimum term, then what is excluded. Add who owns the code and accounts and how either side leaves, in the order of the summary above.

### Can you provide an example of a maintenance contract?

Yes: the agreement summary above, for an imaginary gym booking app on Standard. It sets 18 hours a month, a 2-working-hour reply clock for critical faults and 3 fixed months, then 30 days’ notice.

### Can you transfer an app to someone else?

Yes: Apple and Google both let an app move to another developer account, keeping its reviews and ratings. With us the code and accounts are already yours, so after month three a change of team takes 30 days’ notice.

## Related services

- [iOS app development](https://appagentix.co.uk/services/ios-app-development/)
- [Android app development](https://appagentix.co.uk/services/android-app-development/)
- [Flutter app development](https://appagentix.co.uk/services/flutter-app-development/)
- [MVP development](https://appagentix.co.uk/services/mvp-development/)
- [Software modernisation](https://appagentix.co.uk/services/software-modernisation/)
- [Hire mobile app developers UK](https://appagentix.co.uk/services/hire-mobile-app-developers-uk/)
- [App development cost in the UK](https://appagentix.co.uk/app-development-cost/)
- [Streaming app for phones and TVs: case study](https://appagentix.co.uk/our-work/streaming-service-app/)
- [MyUTHealth patient portal app case study](https://appagentix.co.uk/our-work/myuthealth/)

By [Rohit Kumar](https://www.linkedin.com/in/rohitkumarmaketing/), Co-Founder and COO, AppAgentix. Reviewed November 2026.

[Book a call](https://appagentix.co.uk/requestaquote/)
