Apple reviews every app and every update before it goes live, and Google checks Play Console submissions against its own policies. A clean first submission is usually approved within a few days, but one with problems can go back and forth for weeks while the launch date slips.
Crashes and unfinished screens
Reviewers install the app on a recent device and tap around. A crash, a dead link, a "coming soon" screen or leftover placeholder text is enough to get rejected. Test the release build on real phones as well as the simulator, and take out anything that is not ready.
The reviewer cannot get in
If the app needs an account, put a working demo login in the review notes. If it needs an invite code, a particular location or a piece of hardware, explain how the reviewer can test it. Many rejections come down to the reviewer not getting past the first screen.
Privacy details that do not match the app
Apple’s privacy label and Google’s data safety form have to describe what the app collects. Each permission prompt (camera, location, contacts) needs a reason the user can read, and the privacy policy link has to work.
No way to delete the account
If people can create an account inside the app, Apple requires that they can also start deleting it from inside the app. It is a small feature, and it tends to be forgotten until a reviewer asks for it.
Digital purchases that skip in-app payments
Digital content or features sold inside an iOS app generally have to go through Apple’s in-app purchase system. Physical goods and real-world services, like groceries or a clinic appointment, can use your own payment gateway. Settle which applies before you design the checkout.
A website in a wrapper
An app that only loads your website inside a frame is likely to be rejected for offering too little. It needs something the website cannot do as well, such as notifications, offline access, use of the camera or faster repeat orders.
