Keep your app dependable as platforms change
App maintenance keeps existing products supportable as users, operating systems, stores and dependencies change. The work is planned around your app and agreed capacity, with clear ownership for monitoring, triage and release decisions.
See problems and decide what to fix
Where access and tooling are agreed, review crash and error reports, reproduce issues and classify work by user impact and urgency. Triage produces a clear next action; monitoring does not mean every alert is automatically an included fix.
Maintain compatibility and reduce risk
- Review dependency updates and security notices, then assess compatibility and regression risk before changing versions.
- Check important app flows against supported iOS, Android and store requirements as they evolve.
- Prepare fixes, regression checks, release notes and store builds within the agreed scope and client approval process.
Agree capacity and response expectations
The agreement defines the products, platforms, access, maintenance tasks, capacity and response expectations. There is no universal response-time guarantee or always-on coverage. Hosting, paid monitoring, licences and other third-party charges are identified separately unless included in writing.
Case studies
Luna: a bedtime story where the child is the hero
A bedtime-story app for children around two to nine: parents choose people, pets, a genre and a lesson, and Luna makes the child the hero of a new read-aloud story.
Cleaner Go: finding duplicate photos without uploading any of them
Client work with LabHouse: duplicate and similar-photo grouping on an iPhone, followed by a review flow that lets people keep, delete or undo one decision at a time.
FAQ
Does maintenance include every bug fix?
The agreement defines what capacity covers and how work is prioritized. Larger changes, new features and work beyond that scope are reviewed and agreed separately.
How quickly will an incident get a response?
Capacity and response expectations are agreed for each engagement. There is no blanket SLA; urgent coverage should be explicitly scoped before work begins.
Who approves a release?
The release and QA process is agreed with your team. Your authorized owner reviews and approves production changes and retains control of the relevant accounts.