Choose the release channel
- Apple Developer Program enrolment under your organisation
- App Store Connect roles, bundle identifiers and certificates
- Screenshots for required device classes and accurate metadata
- Privacy “nutrition label” matched to actual SDK behaviour
- TestFlight external testing, review notes and demo account
- Phased release and response to any review questions
- Google Play Console organisation account and verification
- Play App Signing and upload key held safely
- Data safety form completed from an SDK audit
- Content rating questionnaire and target audience
- Internal, closed and open testing tracks as appropriate
- Staged rollout percentage with crash monitoring
- DNS, TLS certificate and domain checks
- Redirect map tested against old URLs
- robots.txt, sitemap and metadata reviewed
- Form delivery tested end to end on production
- Backups configured and restore verified
- Launch-day monitoring and rollback plan
Pre-release audit
Before submission we run a fixed audit: crash-free startup on supported devices, permissions requested in context, account deletion where accounts exist, accurate privacy declarations, working demo credentials, and complete store assets. The result is a short report with pass, fail and fixed items.
After a rejection
If a store rejects a build, we read the guideline cited, reproduce the reviewer's path, fix or clarify, and reply in the resolution centre in measured, factual language. Many rejections are resolved by better review notes rather than code changes.