Your team has product work to deliver, but the maintenance queue keeps returning. Explore a defined slice of app upkeep, with clear ownership, review points and a fixed monthly task allowance that fits your existing process.
For teams with an existing mobile app and an internal technical owner.
Dependency updates, reproducible bugs and release chores compete with the next product milestone. Agree which work can be separated, which needs your team's context and which stays with the roadmap owner.
Agree priorities and acceptance criteria before work enters the queue. Tasks share the agreed capacity, and work in progress stays bounded.
Discuss repository access, branches, code review, test evidence and release approval. Bring a few representative issues and the review process your team already uses.
Keep large changes and architecture decisions visible as distinct work, with their own estimates. The care agreement identifies accepted tasks, supported technology and who performs the release.
This service suits teams that can define priorities and own product decisions. It is assessed around the existing app and your development process.
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.
$750 USD / month
For a stable app that needs routine attention and occasional fixes.
One product. One agreed queue. One task active at a time.
Discuss App Care$1,500 USD / month
For an app with regular maintenance and a queue of small, defined improvements.
The same clear boundaries, with more monthly task capacity.
Discuss App Care Plus| One contained change | A 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 codebases | The 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 review | We 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 improvements | Maintenance 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 limits | One 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 release | Testing 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. |
$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 reviewAn 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.
| Technical acceptance | Native 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 urgency | One 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 cancellation | Monthly 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 systems | Backend 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 responsibilities | You 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. |
An inherited app needs a technical check before anyone can responsibly promise ongoing care.
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.
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.
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.
No. App Care is a defined monthly task allowance. Staffing, access, supported technology and the work allowance are confirmed in the proposal. A request queue does not mean unlimited delivery.
Describe your repository, issue tracking and review requirements. We confirm compatibility and the handover process before accepting work, including who can merge and release changes.
Defined improvements can be considered alongside maintenance. They share the same agreed allowance; discovery, coding, testing and release work all require capacity.
We discuss reprioritising, a larger allowance or a separate estimate. Extra work requires agreement before proceeding.
Describe the estate. Multiple apps, separate native codebases or several backends may need a custom scope rather than one maintenance plan.
Share the app's technology, a few typical tasks and how your team reviews work. We will discuss whether a bounded care arrangement fits.
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