What happens after launch?
Three areas of work run in parallel after launch, each with a named owner agreed beforehand. Operations covers monitoring, crash reporting, alerting and incident response. Maintenance covers dependency and platform updates, certificate renewals and annual operating system releases. Iteration covers improving the product based on analytics and support feedback.
The first month after launch is planned as a stabilisation period, as real usage reveals edge cases that testing cannot fully anticipate.
Crash reporting and structured logging are in place before launch, so issues can be diagnosed quickly.
For iteration, we agree two or three key metrics tied to the product’s goals, which guide decisions more effectively than a large dashboard.
Store accounts, signing certificates, infrastructure credentials and repositories should be registered to your organisation from the start, so you always retain control of your app.
Related service
Mobile App DevelopmentiOS and Android apps from one codebase, with offline support and app store submission.
Was this helpful?