Checklist • Launch
Launch checklist for a mobile app
Published
Most store rejections are not technical. They are missing pieces: a privacy policy that does not open, a test account that does not work, screenshots that do not match the app. The list below covers the ones that come up most often.
Before submission
- The privacy policy is published at a public link that opens without logging in.
- You have a working test account for the review team, with real data in it.
- The icon and screenshots match what the user actually sees, not a mockup.
- The app does not crash when there is no internet connection.
- Every permission requested (location, camera, notifications) has a visible explanation.
Store-specific requirements
- Apple: if the app has accounts, it must also offer in-app account deletion.
- Apple: paid digital content consumed inside the app must be sold through in-app purchase.
- Google: the data safety declaration must match what the app actually does.
The first week after launch
- Track how many open the app a second time. It is the only metric that matters early on.
- Read the first reviews and reply to them. The next users will read them.
- Ship a small update within the first days. It signals the app is alive.
How 4myapp helps
4myapp generates the signed builds and prepares the store-required assets from the same project where you built the screens. The privacy policy and account-deletion page are generated with your company's details, so they stop being a reason for rejection.