Discipline — Release & publishing
Release and publishing
We prepare and submit app store releases and carry out website go-lives to a written procedure, so publication is a checked step rather than a gamble.
Store approval is controlled by Apple and Google. We plan for review time; we do not promise it.
Procedure
Accounts and access
Developer accounts are registered to your organisation. We are invited as team members with the minimum role needed, and access is removed at the end of the engagement if you wish.
Store listing
- Name, subtitle and description drafted for clarity
- Screenshots produced at each required size
- Support and privacy URLs confirmed live
- Age rating and content questionnaires completed
Privacy declarations
App Store privacy details and Google Play data safety forms are completed from an inventory of what the app and its third-party libraries collect. The declarations are checked against your privacy policy so the two say the same thing.
Submission and review
Builds are submitted with reviewer notes and test access. Questions or rejections are answered with reference to the specific guideline cited; we correct and resubmit.
Website go-live
- DNS and certificate verification
- Redirects from previous addresses
- Forms tested on the production domain
- Error pages, sitemap and robots file checked
- Backup confirmed before switch-over
Staged rollouts
Where the store supports it, we recommend phased releases so that a problem affects a small share of users and can be paused. For websites, we schedule go-lives early in the working week, with a rollback plan written and tested.
What we will not do
We do not purchase reviews or installs, use misleading listing practices or submit declarations we cannot substantiate. These carry real risk of removal from the stores.
Plan a release