Support and maintenance

A published application is not finished. Apple and Google change their requirements every year, operating systems move on, devices are replaced and the business itself changes the process the app was built for. This service keeps a live application working and useful instead of quietly decaying until it stops.

Enquire about this service

Abstract geometric illustration of a repeating cycle of blocks arranged around an open square

What this involves

Support begins with a review of the current build: dependencies, crash reports, store compliance and anything about to expire. We then run the application on a regular cycle — monitoring errors, updating libraries and testing each new OS release before your staff receive it, so a September iOS update does not become an October emergency. Change requests are estimated individually and released in planned batches rather than as one-off patches, which keeps testing sensible. You get a named contact, an agreed response time for faults and a short written report of what changed in each release.

What’s included

  • Review of the existing build, dependencies and crash reports
  • Crash and error monitoring with alerts
  • Library, SDK and dependency updates
  • Testing against new iOS and Android releases before your staff get them
  • Store compliance: privacy declarations, Data safety, rating questionnaires
  • Certificate, provisioning profile and signing key renewals
  • Agreed response times for faults
  • Planned release batches for improvements and change requests

Deliverables

  • Release notes for every update
  • Monitoring dashboard access
  • Updated documentation after each change
  • Periodic report on stability, adoption and store status

Technologies

  • Firebase Crashlytics
  • Sentry
  • GitHub Actions
  • Fastlane
  • App Store Connect
  • Google Play Console

Timelines and pricing

Timelines and pricing are quoted per project after a discovery call. The estimate follows the discovery call and covers the scope, the stages and the payment schedule, so there is nothing to sign before you have seen it in writing.

Questions about support and maintenance

Can you take over an app another agency built?

Yes, and it is a common request. We start with a technical review of the code, the dependencies and the store accounts, then give you a written assessment of the state it is in and what it will take to support. Occasionally that review concludes that a rebuild is cheaper than maintenance, and we will say so.

What counts as a fault rather than a change request?

A fault is the application not doing what the agreed specification says it does. A change request is the specification itself changing. Faults are covered by the support arrangement; changes are estimated separately, so you always know which side of the line a piece of work sits on.

What happens if we stop the support arrangement?

The application keeps running and the code stays yours. What stops is monitoring, OS-release testing and store compliance work, which means the risk of an interrupted listing or a broken update moves to you. We hand over documentation and access so another team can take it on.

Enquire about this service

Send the details of your project and we will reply with questions and a suggested next step.

Go to the enquiry form

Enquire about support and maintenance

Fields marked with an asterisk are required. Your details are used to answer this enquiry only, as set out in our Privacy Policy.

Platform (required)
For example: start in six weeks, launch before the new financial year.
Tell us what the app needs to do and who will use it.

Documents and existing specifications can be sent to [email protected]. We reply to every enquiry.