Engineering guides / App maintenance and rescue
By Arte Soft engineering · 24 October 2026
Scoping an iOS maintenance retainer around the product’s actual risks
A maintenance retainer should explain what ongoing work it buys and how priorities are chosen. “We keep the app running” is too vague when the product depends on Apple releases, third-party services and client decisions. Define the supported system and a practical process for incidents, updates and small improvements.
The decision to make
Start with a baseline assessment of build health, ownership, dependencies and known defects. A recurring agreement should not conceal a large inherited stabilization project inside an ordinary monthly allowance. Separate one-time recovery from routine maintenance so both sides know whether current capacity is paying down old risk or keeping a stable product current.
Name the coverage: native app, backend, store configuration, infrastructure and support investigation may have different owners. Distinguish incident acknowledgement, diagnosis and resolution; they are not interchangeable promises. Any availability or response commitment should be agreed explicitly against staffing and monitoring rather than implied by a contact form or a broad service description.
A useful scope of work
A sensible scope includes issue triage, dependency review, platform compatibility checks and a prioritized maintenance backlog. Record how small changes are estimated and what happens when requests exceed the agreed capacity. Schedule release decisions and physical-device verification where needed. Updating a dependency is not automatically beneficial if it creates untested behavior in an important integration.
Report outcomes rather than activity totals alone. Summarize resolved user-impacting problems, verified compatibility work, remaining risks and decisions needed from the owner. Keep a reproducible candidate and release history. For each production change, agree authorization and rollback responsibility. A maintenance relationship should increase the client’s operational visibility rather than deepen dependence on one supplier.
Acceptance checks to agree before delivery
A retainer should be accepted as a defined operating arrangement with observable outcomes. Review inherited risk before routine work begins, then inspect coverage and reporting over time. These checks keep capacity, ownership and release evidence clear without implying unlimited changes, permanent monitoring or a resolution promise that has not been agreed.
- Create a baseline inventory that separates inherited defects, routine maintenance and planned feature development.
- Give each incoming issue an impact, owner and next step without promising an unsupported resolution time.
- Deliver a recurring report tied to shipped or verified outcomes, known risks and client decisions.
- Maintain build instructions and release records so another authorized developer can take over the supported product.
Constraints and what to send us
Send the current app and server architecture, release frequency, support volume and essential integrations. Define time-zone coverage and emergency expectations explicitly if needed. Store policy changes and provider outages may require separate decisions or work. A useful proposal identifies exclusions and capacity limits; it should not imply unlimited features, permanent monitoring or guaranteed approval for every release.
Our own product reference and a starting engagement
Maintenance assessment and a scoped support agreement. Cloud Calendars and Reel Screen Recorder are owned published products with ongoing release needs, providing inspectable product context. Their existence does not establish a service-level promise. Begin with a baseline review, then agree coverage and reporting against the risks and ownership of your application.
Relevant Arte Soft work
Cloud Calendars: Sync & Widget is our own product or engineering project. It provides context for the work we discuss here; it is not a claim of identical results for every client deployment.
Sources and further reading
Need help with Maintenance assessment and a scoped support agreement?
Send the current app, system or brief, the behaviour you need and your constraints. We can agree a discovery, implementation or repair scope with concrete acceptance criteria.
Discuss this with Arte Soft