After release
Looking After an App Once It Is Live
Launch is the start of an application's working life, not the end of the job. This service keeps a published app building, passing store review and behaving properly for the people who rely on it.
Why does a live application need managing?
Because the ground under it keeps shifting. Phone operating systems get new versions, app stores revise their rules, outside services retire old interfaces and libraries turn out to have security flaws. Left alone, a published app eventually stops building, gets flagged in review or breaks for a share of its users, usually at an awkward moment.
Whose applications are managed?
AARVYA CORPORATION looks after applications it has published itself and, under an agreement, applications that belong to clients. On a client’s application the client stays its owner and end provider, and our part is the management work that was agreed.
Ownership, stated plainly
Some of the products AARVYA CORPORATION works on are its own and some belong to clients.
For an application or digital product that AARVYA CORPORATION owns, responsibility for it rests with AARVYA CORPORATION.
Carrying out development, management or advertising work on a client's product does not change who owns it: the client keeps ownership unless a written agreement says otherwise.
What does ongoing management cover?
- OS Version Readiness
- Store Rule Changes
- Library Security Fixes
- Bug Triage
- Scheduled Releases
- Crash Monitoring
- Speed Checks
- Roadmap Upkeep
Is any part of this page unclear? Write to aarvya.corporation@gmail.com and say which part, and the reply will explain it.
