App Care for business operations

Keep the app
your business relies on
moving.

When your app supports bookings, customer accounts or work in the field, maintenance needs a clear place in the operating plan. Discuss the journeys that matter, the systems behind them and the support your business actually needs.

For existing customer and staff apps. Support arrangements agreed to fit the scope.

Review before commitment. Understand the app and access first.A finite monthly task allowance. Accept and prioritise a clear queue.You approve the scope. Extra work needs a separate agreement.
The work behind a maintained app

Begin with the work
the app helps people do.

A working screen does not tell the whole story. A booking may depend on a calendar, payment provider and confirmation message. A staff task may depend on permissions, an API or offline sync.

  1. 01

    Name the critical journeys.

    Identify the actions customers or staff need to complete and what happens when they cannot. Your maintenance scope should identify the dependencies and who is responsible for each one.

  2. 02

    Plan checks around real work.

    Agree representative test journeys, supported devices and who signs off a release. Your business should know what is changing before users receive an update.

  3. 03

    Clarify the handovers.

    Record which issues belong to the mobile app, backend, hosting provider or another supplier. Agree access requirements, release responsibilities and limits of cover.

Check the fit

A maintenance plan
with a business owner.

The right care arrangement brings technical work and business decisions together. Nominate someone who can explain priorities and approve the outcome.

A sensible fit for ongoing care

  • An existing customer or staff app supports a defined business process.
  • You can arrange source access and an owner for app, store and connected-service accounts.
  • Someone in your team can prioritise issues, supply safe test cases and approve releases.

A different starting point may help

  • High-risk, regulated or safety-critical operations need specialist requirements reviewed before any support commitment.
  • A new business workflow, major integration or platform migration may need a separate project.
  • An immediate outage or a round-the-clock support requirement needs a separately agreed incident arrangement.
One shared care system

Fixed monthly care.
Clear scope.

Choose a plan for one existing mobile product. Native and hybrid apps are welcome, including iOS and Android. We confirm your technology, code and release setup before accepting the app. Your monthly price is fixed for the agreed scope.

For occasional maintenance

App Care

$750 USD / month

For a stable app that needs routine attention and occasional fixes.

  • One monthly review of agreed dependencies, available crash reports and relevant store requirements
  • Up to 2 accepted maintenance tasks per month
  • One planned release cycle per month for approved, ready changes
  • A monthly summary of work completed, open issues and next priorities

One product. One agreed queue. One task active at a time.

Discuss App Care
What counts as a task?
One contained changeA task is one contained change to one existing screen or function in one codebase, with one agreed acceptance criterion. Examples include fixing a reproducible validation error, updating an isolated compatible dependency or, on App Care Plus, adjusting an existing screen’s layout or text.
Native and shared codebasesThe same change in separate native iOS and Android codebases counts as two tasks. A shared-codebase change counts as one task when it fits the same boundary; supported-platform testing is included in that task.
Accepted after reviewWe reproduce or review the request before accepting it into the care queue. Investigation may show that a separate project is needed. A task slot is not an unlimited repair obligation.
Maintenance and improvementsMaintenance addresses existing functionality and routine upkeep. In App Care Plus, a small improvement must fit the same contained-change boundary. New screens, substantial features, integrations, redesigns, major framework/OS migrations, architecture changes and substantial backend changes need a separate fixed quote.
Monthly limitsOne task is active at a time. Unused monthly task slots do not roll over. Accepted tasks remain in the queue until completion without using another task slot; timing depends on scope, access and approvals. Extra work requires an approved fixed quote before it begins; no hourly overage is automatically added.
Review and releaseTesting covers accepted changes against the agreed device and OS list. One planned release cycle each month includes preparation and submission to the agreed stores when changes are ready and approved. Store decisions and review times remain with Apple and Google.
Establish the baseline

App baseline
assessment

$500 USD once

For one mobile product with up to two mobile codebases and accessible source and store accounts. The assessment covers an access and dependency inventory, a build attempt for each included codebase, a review of available crash and store notices, and a written priority list with a care recommendation.

This is an assessment, not a repair package or a comprehensive security audit. We confirm eligibility and access before you agree to it. Larger estates, missing access or specialist assessment requirements receive a separate fixed quote before work begins. Recovery or catch-up work is also quoted separately. There is no obligation to buy ongoing care.

Request an app-care review

Need recovery
or a major change?

An app that will not build, has substantial inherited issues or needs a major new feature may need a separate project first. We agree that scope before starting ongoing care. Rebuilds, major migrations and new integrations are not automatically covered by a maintenance plan.

Care prices are in USD per month. Monthly billing starts after the app is accepted and the start date is agreed. Applicable taxes and third-party fees are identified separately in your proposal. Sending an enquiry does not start a subscription or authorise paid work. Store accounts, hosting, software subscriptions and third-party usage charges are separate. App Care Plus covers agreed small improvements; it does not include advertising, customer acquisition or a revenue guarantee.

Clear responsibilities before care begins.
Technical acceptanceNative iOS, native Android and hybrid apps can be considered. We confirm source access, build and release readiness, supported platforms, dependencies and existing issues before accepting ongoing care.
Support and urgencyOne nominated contact and an agreed request channel. Support hours, time zone, severity rules and response arrangements are confirmed in your proposal. A response target is different from a fix estimate. No 24/7 cover or guaranteed resolution time is included. Do not use this enquiry form as an emergency support channel.
Billing and cancellationMonthly in advance, with a one-month minimum. Cancel with 30 days’ notice; service ends at the end of the paid monthly period that falls at least 30 days after notice. No annual commitment.
Connected systemsBackend work, hosting, monitoring and security maintenance are included only where explicitly scoped. Your proposal identifies who owns each connected service and who handles issues outside the mobile app.
Customer responsibilitiesYou keep ownership of your accounts, arrange approved access and nominate someone to prioritise work, provide safe test cases and approve releases. Do not send credentials, source code or customer records through this form.
Start with the app you have

Review first.
Agree the next step.

An inherited app needs a technical check before anyone can responsibly promise ongoing care.

  1. 01

    Describe the problem.

    Share your public app link, the platforms involved and the issue you want to address. You can start even if you do not know the technology.

  2. 02

    Check condition and fit.

    We review your request and confirm eligibility for the $500 baseline assessment or quote any different assessment upfront. Existing problems, access and dependencies inform the recommendation.

  3. 03

    Choose an agreed scope.

    You receive a care proposal at the published plan price, a separately scoped project recommendation or an explanation of why the app is not a fit. Paid work starts only after agreement.

Before you decide

Your app.
Your questions.

Does app care include our backend and hosting?

Only where the proposal expressly includes them. We identify relevant services and responsibilities before starting. Supplier subscriptions, hosting charges and substantial backend changes are separate unless agreed otherwise.

Can you guarantee uninterrupted service?

No. A maintenance plan does not guarantee uninterrupted availability or control the services your app depends on. Required response arrangements and contingency responsibilities need to be agreed for your situation.

What if we need urgent or out-of-hours support?

Tell us before choosing a plan. Availability and escalation arrangements must be agreed separately; this enquiry page does not offer round-the-clock incident response.

Who approves updates?

Your agreement identifies the approver and the test and release process. App-store decisions and review times remain with Apple and Google.

What if the app handles sensitive or regulated information?

Describe the category of information, without sending actual records. Suitability, access controls and any specialist requirements need review before work is accepted. No compliance certification is implied.

A useful first step

Which workflow
needs a clearer plan?

Share the app, its main business use and any support requirement. We will discuss the scope before recommending care.

What happens next

Our team reviews your request and follows up by email. We clarify the app’s condition, access and priorities, then agree any assessment and the right next step. You see the scope and costs before paid work starts.

Prefer email? team@afinitiglobal.com

Tell us about your app.

Start with what you know. “Not sure” is a useful answer. Please use public links and leave out passwords, source code and customer data.

Native and hybrid apps can be considered. We confirm fit after reviewing the codebase.

A public App Store, Google Play or website link. Do not include private access links.

For example: customer booking, order status or a staff task. Explain the effect and any known deadline, without sharing customer or staff records.

We record your enquiry in HubSpot CRM. This does not subscribe you to a newsletter.

This enquiry does not purchase a plan, book paid work or authorise access to your systems. Privacy policy.