Guideline 4.2 rejection: Minimum Functionality
How the rejection usually reads: "Your app provides a limited user experience as it is not sufficiently different from a mobile browsing experience"
Why it happens
A WKWebView wrapped around a website with no native navigation, no offline behaviour and no device features is the classic 4.2 rejection. The scan looks at the ratio of web view usage to native UI classes; the fix is product work — native tabs, push, offline caching, camera or share integrations — not a code tweak.
What can be checked before you submit
1 of RejectProof’s checks map to Guideline 4.2. Each one reads your .ipa — no upload — and reports the evidence with a fix.
- Looks like a website wrapper (minimum functionality)
PB-20 · guideline 4.2 · warning
To be accepted, your app must offer more than a website opened in a browser: native navigation, offline support, device features, etc. If it only shows a website, consider adding native functionality.
What a scan cannot tell you
Static checks read the build; they do not run it. Whether a reviewer likes your design, agrees with your content, or considers the app “sufficiently different” is their call. Fix the mechanical layer first so the human review is about your product, not about a missing plist key.