Freeze and test the release candidate
Choose a version number and build identifier, then make a release candidate from a clean source revision. Test first launch, a completed round, settings, save restore, interruption and resume, and a fresh install. Verify every control on the intended screen sizes and orientations. If an issue requires a code change, rebuild and rerun the affected checks against the new artifact; do not assume a debug build is equivalent to the candidate.
Collect the materials your listing needs: app name, description, screenshots from the current build, age and content answers, support contact, privacy disclosures, and any in-app purchase information. Confirm that the store’s current rules and target requirements apply to this specific release. Avoid basing a schedule on a fixed review duration or an old API cutoff.
Use the platform’s staged submission route
For Google Play, create the app in Play Console, complete the dashboard setup, upload an Android App Bundle, and select an appropriate testing or release track. The Play Console documentation says the package name is unique and permanent, so settle it before your first upload. Read current target API and testing requirements in the console before scheduling launch.
For Apple, create the app record in App Store Connect, select the build, complete required metadata, and submit for App Review. TestFlight can distribute beta builds and collect feedback before release. Apple distinguishes adding a build to a submission from actually submitting it; check the submission state and confirm the final action is complete rather than assuming an upload is already under review.
Make the release repeatable
Store the release artifact, source revision, build settings, changelog, and submission notes together. Track which version is live in each store. If you also ship a web edition, test the hosted route and mobile browser layout separately.
Questions about publishing a mobile game
Should I release both mobile platforms at once?
Only if both builds and submissions are ready. Independent platform review and release steps can diverge, so state clearly which version is available and keep its notes tied to the platform.
Can the same test checklist cover a web game and a store app?
Some gameplay checks can be shared, but packaging, install, permissions, update, and review steps differ. Keep a common gameplay smoke test plus platform-specific release checks.