Rejection guides / Guideline 4.2: Minimum Functionality

Updated November 2026 · Appflight

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.

Explain my rejection

Likely causes

What usually gets it through

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.

Explain my rejection

Related guides

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)