Section 03 · Care
Care you can see
Good support should not be invisible. You should see what is happening to your app every month.
03.1 Three levels of care
01
Watch
dependency and SDK updates, crash monitoring, monthly report
for stable apps with infrequent change
02
Care
everything in Watch + prioritised bug fixing, preparation for new OS versions
for products with active users
03
Grow
everything in Care + a planned monthly allowance for new features
for products that are growing
Pricing is agreed individually after reviewing the app.
03.2 Request priorities
- P1 — critical
- app will not start, or payment/sign-in unavailable for many users; handled first during working hours
- P2 — important
- a feature is broken but a workaround exists; scheduled for the next cycle
- P3 — normal
- cosmetic issues and wishes; added to the monthly plan
03.3 What the monthly report contains
- List of changes with build references
- Dependency health: what has aged and the risk
- New App Store / Google Play requirements that affect you
- Most frequent crashes and their status
- Proposals for next month with estimates
03.4 Taking over existing code
We take over apps built by other teams. We start with an audit: does the project build, what the risks are, what to fix first. The audit is a standalone deliverable you keep regardless of further work.
The first rule of care: break nothing until you understand how it works.