Rejection guides / Guideline 4.2: Minimum Functionality
Guideline 4.2 - Design - Minimum Functionality, explained
Apple is saying the app doesn't do enough to justify being an app. The most common case is a website wrapped in a web view.
"Your app should include features, content, and UI that elevate it beyond a repackaged website."App Review Guideline 4.2, Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Likely causes
- The app is mainly a web view of your website, with little that uses the device.
- It's primarily marketing material, ads, web clippings, a content aggregator or a collection of links, which 4.2.2 names.
- It needs another app installed to work at all, which 4.2.3(i) covers.
- It downloads large resources on first launch without saying how big they are or asking first, under 4.2.3(ii).
- It's a template or app generator build submitted for a client, which 4.2.6 covers separately.
- It's a single simple feature that a website or a built-in app already does.
What usually gets it through
- Add native features that use the device in ways a website can't: push notifications that matter, offline access, widgets, camera, location, sharing, Siri or Shortcuts.
- Replace key web screens with native UI, especially navigation, sign-in and the main flow.
- Make the core use clear in the first minute. Reviewers judge what they can see quickly.
- In your reply, list the native features and where to find them. Point to things a reviewer can try.
There is no official feature count that clears 4.2. What matters is whether the app gives lasting value or adequate utility, in Apple's words.
Common questions
- Will Apple accept a WebView app?
- Apps that use web views can be approved, but the guideline asks for features, content and UI beyond a repackaged website. A wrapper with nothing native is the classic 4.2 rejection.
- Will adding push notifications alone fix 4.2?
- Sometimes, but rarely on its own. Reviewers look at the whole experience. Several native features that make the app more useful than the website give you a stronger case.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 4.3: Spam
- App Review Board: How to appeal a rejection
- Guideline 2.1: App Completeness (crashes, bugs, placeholders)
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)