Table of contents
- Quick read
- Readiness check
- Freeze the build and record the version
- Prepare store metadata and screenshots
- Confirm signing keys and entitlements
- Run the policy checklist before submission
- Stage the rollout and watch the first days
- Keep a rejection and hotfix path ready
- Close the release record
- Role brief
- Frequently asked questions
- Sources
Is the handoff ready?
Use these checks before access expands or the first ticket begins.
Build record
Ready: Attach commit, build number, toolchain, artifact, and checksum.
Needs work: The lane has no written record for this check.
Listing
Ready: Record metadata, screenshots, privacy answers, and policy URLs.
Needs work: The lane has no written record for this check.
Signing
Ready: Name the key owner, expiry date, and client-controlled backup.
Needs work: The lane has no written record for this check.
Rollout
Ready: Set the percentage, pause thresholds, and revert path in advance.
Needs work: The lane has no written record for this check.
Freeze the build and record the version
Freeze the release branch and record the commit, the build number, and the version name. Note the dependency lockfile and the toolchain versions used for the build. Keep the artifact and its checksum in a place the client can retrieve. A store release that cannot be rebuilt from a recorded commit is impossible to audit.
Record the device and operating-system versions used for the release test. Note the features gated by the app version and the server version they require. Check that the store build points at the production API and not a staging host. A build with the wrong endpoint is the classic release failure that the checklist exists to catch.
Prepare store metadata and screenshots
Record the title, subtitle, description, keywords, and category for each store listing. Note the screenshots and preview videos with their device sizes and the date captured. Check that the text matches the current feature set and the legal disclosures the client requires. Metadata that describes a removed feature invites a review rejection.
Record the privacy questionnaire, data-collection disclosure, and tracking permission text. Note the account-deletion path and the support contact that the store requires. Check that the policy URLs resolve without a login. A listing that points at a stale privacy page can delay the whole release.
Confirm signing keys and entitlements
Record which signing key and provisioning profile built the release and who holds the key. Note the certificate expiry date and the backup location under client control. Check that the entitlement list matches the features in the build. A signing key held by one contractor is a release risk that outlives the contract.
Record the app identifier, bundle version, and any associated domains or push configuration. Note the store account owner and the role used to upload the build. Check that the upload account has the minimum role needed and that the client can revoke it. The release should not depend on a personal account nobody can recover.
Run the policy checklist before submission
Check the store rules that most often affect the product, such as payments, health claims, location use, and account deletion. Record the rule, the screen that satisfies it, and the person who verified it. Note the features that need a disclosure or an age rating. A policy check after submission turns a small fix into a review cycle.
Check that every permission has a visible purpose string and a path that works when permission is denied. Note the screens that request background location, contacts, or notifications. Record the test result on a clean install. A permission prompt with no explanation is a common and avoidable rejection.
Stage the rollout and watch the first days
Choose the rollout percentage and record the reason and the owner who approved it. Note the crash-rate and support-ticket thresholds that pause the rollout. Keep the previous build available for a fast revert where the store supports it. A staged rollout is only useful when the pause rule is written before the release.
Watch the first-day crash rate, startup time, and the top support contacts by version. Record the baseline from the previous version so the comparison has meaning. Note the store review status and the release time in each region. The first day is when a device-specific failure appears, not in the internal test pass.
Keep a rejection and hotfix path ready
Record the reviewer contact, the store appeal path, and the evidence the team will send for a disputed rejection. Note the person who can authorize a resubmission and the customer message for a delay. Keep the build and metadata versions that were submitted. A rejection handled from memory loses the exact text that caused it.
Write the hotfix rule for a release that must ship outside the normal train. Record the approver, the test scope, and the store review time the team expects. Note the rollback if the hotfix fails review. A hotfix path without a rollback is a second release risk stacked on the first.
Close the release record
Store the final build, the store listing version, the review outcome, and the rollout history in one release record. Record the date each store approved the build and the version that reached production. Note any policy warning that should be fixed before the next release. The record should answer what shipped, when, and to whom.
Review the checklist after the release with the offshore mobile lead and the client owner. Record the steps that were skipped and the step that caught a real problem. Update the checklist with one change and an owner. A checklist that never changes after a release is a formality rather than a control.
Copy-ready brief
Put the operating agreement in writing.
Record the release commit, build number, and production endpoint check.
Match each store rule to a screen and a verifier before submission.
Use a client-owned store account with the minimum upload role.
Keep the submitted build, listing version, review outcome, and rollout.
Frequently asked questions
Who should own the signing key?
The client should own and back up the key, with the delivery team granted the narrowest role it needs.
Can the team skip the staged rollout?
Only with a recorded reason and a faster pause rule, because a full release reaches every device at once.
What if the store rejects the build?
Use the recorded appeal path and the exact submitted metadata, then resubmit with the fix and a new build number.
Do screenshots need to match every device?
Match the sizes the store requires for the devices in the support matrix and date each capture.
Sources
- Apple App Store Review Guidelines
The policy rules a submitted build must satisfy.
- Google Play Developer Policy Center
Play policy areas including payments, privacy, and permissions.
- Apple provisioning and code signing
How profiles, entitlements, and signing keys relate.
- Android app signing
Key management and upload signing for Android releases.
