App Store and Play Store review can feel like a black box, but most rejections come down to a small, predictable set of issues. Catching them before you submit saves days, sometimes weeks, of back-and-forth with review teams.
Before you submit
- Every feature that requires a login has a working demo account for the reviewer
- Permissions requests (camera, location, notifications) each have a clear, honest usage description
- No placeholder content, broken links, or Lorem Ipsum anywhere in the shipped build
- Sign-in with Apple is offered if you support any other third-party login on iOS
- In-app purchases, if any, are configured and testable before submission — not added after
- Privacy policy and terms links are live, accurate, and match what the app actually does with data
Test on real devices, not just simulators
Simulators don't catch everything — camera behavior, push notification permissions, biometric prompts, and performance on older or lower-memory devices all behave differently on real hardware. We run every build through manual testing on physical devices before it goes anywhere near submission.
Read the guidelines for your category
Apple and Google both publish detailed review guidelines, and they update them. An app in a regulated category — health, finance, kids — has extra requirements that a generic checklist won't catch. Part of our QA process is checking your specific category's current guidelines, not just the general ones.
None of this guarantees a same-day approval. But it removes the avoidable reasons for rejection, which is most of them.