Skip to content

Service · Support

App Maintenance Support

Commission retained support when your app is live and you need it kept healthy without building a full in-house team. We agree response terms with you, watch the app in production, keep it current with each OS and store requirement, and fix what breaks under a support arrangement you can budget for.

Response terms agreed per severity in writing

OS and store deadlines tracked ahead of time

Takeover audit for apps built by others

Deliverables

What an app maintenance support engagement delivers.

01Delivered

A written support agreement

Severity definitions, the response and resolution targets we agree with you for each, support hours, how issues are raised and who on both sides is accountable.

02Delivered

Production monitoring

Crash reporting, error tracking, uptime checks on the services the app calls and alerts routed to the on-call engineer, with dashboards your team can also see.

03Delivered

Platform and dependency upkeep

Builds updated for each major iOS and Android release, target SDK levels raised to meet Google Play deadlines, and libraries upgraded on a schedule rather than in a panic.

04Delivered

Store compliance

Privacy declarations, data safety forms, required account deletion flows, permission justifications and policy notices from Apple and Google handled before they block a release.

05Delivered

A small-change allowance

An agreed amount of capacity for minor improvements, copy changes and configuration updates, so small requests do not each need a new contract.

Early decisions

Technical decisions we settle early in app maintenance support.

01Decided

What each severity level means

An outage of payments, a crash for some users and a layout glitch need very different responses. We define the levels around your business, not a generic template, and attach targets to each.

02Decided

Support hours and on-call

Business-hours cover suits many apps; others need out-of-hours response for critical issues. The choice drives staffing and price, so it is set before the agreement starts.

03Decided

Who holds production access

Cloud accounts, store consoles, signing keys and third-party services should belong to you. We agree the least access we need and how it is granted and revoked.

04Decided

Upgrade cadence

Dependencies can be upgraded continuously in small steps or in planned batches. Small steps reduce risk; batches suit apps with heavy manual testing. We pick what fits your release process.

05Decided

Boundary between support and new work

Fixing a defect is support; building a new feature is project work. Agreeing the line, and how larger requests are estimated, avoids disputes later.

Engagement

How an app maintenance support engagement runs.

  1. 01Phase 1

    Takeover audit

    For an app we did not build, we review the code, build process, dependencies, monitoring and store standing, and list the risks that need attention before support terms begin.

  2. 02Phase 2

    Access, monitoring and runbooks

    Accounts are transferred or shared under the agreed access rules, monitoring and alerting are set up, and runbooks are written for releases, rollbacks and common incidents.

  3. 03Phase 3

    Steady-state support

    Issues are triaged and fixed against the agreed targets, the platform calendar is worked through ahead of deadlines, and releases go out through the staged process.

  4. 04Phase 4

    Regular reviews

    At agreed intervals we report incidents, upgrades completed, upcoming platform deadlines and technical debt worth paying down, and adjust the agreement if your needs have changed.

Fit

When retained app support is the right choice.

01Good fit

The build team has moved on

When the agency or contractors who built the app have finished, someone still needs to keep it running, updated and accepted by the stores.

02Good fit

You cannot justify a full mobile team

Apps that need steady care rather than constant new features are often better served by a retained arrangement than by permanent hires.

03Good fit

Store deadlines keep catching you out

If past releases have been blocked by a target SDK requirement, an expired certificate or a privacy declaration, scheduled upkeep stops it happening again.

A live app is never finished

Even an app nobody touches will decay. Apple and Google release new OS versions every year, raise the minimum SDK and toolchain levels they accept, and add privacy and policy requirements. Libraries publish security fixes, push certificates and signing credentials expire, and the backend APIs the app calls change underneath it.

None of that is dramatic on its own. Left alone for a year or two, it adds up to an app that cannot be updated at the moment you most need to ship a fix.

Agreeing what support means

Support arrangements fail when each side imagines something different. We write down what counts as each severity, how quickly we respond and aim to resolve each level, which hours are covered and how issues reach us. We also write down what is not support, so a request for a new feature is recognised and estimated rather than silently absorbed.

Watching the app, not waiting for complaints

If the first sign of trouble is a one-star review, monitoring has failed. We set up crash reporting, error tracking and uptime checks on the services the app depends on, and route alerts to the engineer on duty. Patterns in crash data often point to a problem days before users would have reported it.

Keeping pace with Apple and Google

Google Play requires apps to target a recent Android API level and publishes the deadlines in advance. Apple raises the minimum Xcode and SDK version for submissions and announces upcoming requirements on its developer site. Both stores require apps that create accounts to let users delete them. We keep a calendar of these dates and schedule the work ahead of each one.

Taking over an app someone else built

Many support relationships start with an app built elsewhere. Before agreeing response targets, we audit the code, check that it builds from a clean machine, confirm who holds signing keys and store access, and list risks such as outdated dependencies. That audit sets honest expectations and often reveals a few urgent fixes worth making first.

FAQ

Questions to resolve before the build.

01What affects the cost of app maintenance?

The number of apps and platforms, the size and age of the codebase, support hours and response targets, how much monitoring the backend needs, the volume of third-party dependencies, and the size of the small-change allowance. A takeover of an unfamiliar app also includes the initial audit.

02How quickly do you respond to issues?

Response and resolution targets are agreed per severity in the support agreement, based on your business needs and the support hours you choose. We do not quote a single standard figure because a payment outage and a cosmetic glitch should not share one.

03What do we get from a support arrangement?

Monitoring and alerting set up in your accounts, runbooks, a maintained platform calendar, fixes and upgrades released through your pipeline, regular reports, and an up-to-date handover pack if you later move support in-house or elsewhere.

04Who owns the code and accounts while you support the app?

You do. Code stays in your repositories, apps stay in your store accounts and cloud resources in your subscriptions. We work through access you grant and can revoke, and all changes are committed under your ownership.

05How is support work accepted?

Fixes are confirmed by the person who raised the issue, or against the reproduction steps in the ticket. Upgrades are accepted when the agreed regression checks pass and the release reaches full rollout without a rise in crashes.

06What does maintenance not include?

New features beyond the small-change allowance, redesigns, major rewrites and marketing work are scoped separately. Outages caused by third-party services are investigated and worked around where possible, but their fix lies with the provider.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Google Play: target API level requirements

    Google’s rules and deadlines for the Android API level apps must target.

  2. 02
    Apple Developer: upcoming requirements

    Apple’s announcements of new SDK, privacy and submission requirements.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.