Navigating App Review — Getting Approved First Time

Apple receives approximately 100,000 app submissions per week and reviews most within 24–48 hours. Review is performed by human reviewers using a combination of automated scanning (for known patterns and API usage) and manual testing. Reviewers work from a detailed rubric based on the published guidelines — they're not making subjective aesthetic judgments, they're checking compliance. The most common rejection reasons, in order: privacy violations or missing privacy policy, crashes during review, broken or placeholder content, guideline 4.2 (minimum functionality — app does too little to be useful), guideline 3.1.1 (using non-Apple payment for in-app purchases), misleading metadata, and inappropriate content rating. Reviewers test your app on a physical device. They will try to trigger edge cases, network failures, and unusual input. If your app crashes on an older supported device (your build target includes, say, iOS 16, but you only tested on your personal iPhone 15 Pro), it will fail review. Use BrowserStack or TestFlight with diverse device test coverage before submitting.

Rejection is common — approximately 40% of new apps are rejected on first submission. Don't be discouraged, and don't panic. Read the rejection message carefully — Apple's reviewers are specific about what caused the rejection and often include screenshots of the issue they found. For rejections you disagree with, use the Review Board appeal process in App Store Connect. This escalates to a senior reviewer. Write a detailed, professional explanation of why your app complies with the guideline in question. Reference specific guideline numbers. Attach evidence if relevant (screenshots of your privacy policy, documentation of your testing). The appeal usually resolves within 5–7 business days. For accessibility apps specifically (BathCheck, ShowerBuddy), be aware of guideline 5.1.1 regarding health and medical apps. Apps that make health claims or provide clinical decision support face additional scrutiny. BathCheck as an assessment documentation tool is in a safer category than, say, an app that claims to diagnose medical conditions. Framing your app description carefully — focusing on workflow and documentation rather than clinical recommendations — reduces this risk significantly.