App Rejected for Minimum Functionality: How to Fix Apple Guideline 4.2 (2026)

If your app was rejected for minimum functionality, App Review is citing Guideline 4.2: the app does not do enough, natively, to justify being an App Store app rather than a website. The fix is rarely a bug fix. It is adding real app-level value, removing the "repackaged website" pattern, and explaining those changes clearly when you resubmit.

What "minimum functionality" means under Guideline 4.2

Apple's App Store Review Guidelines put this under section 4 (Design). The core instruction is that an app should offer features, content, and UI that go beyond "a repackaged website." If the app is not useful, unique, or app-like, or does not provide lasting entertainment or adequate utility, it may not be accepted.

The sub-clauses are where most rejections actually land:

• 4.2.2 – Apps (other than catalogs) should not primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links.
• 4.2.3 – The app must work on its own without requiring another app to be installed, and if it downloads extra resources on first launch, it must disclose the size and prompt the user first.
• 4.2.6 – Apps built from a commercialized template or app generation service are rejected unless the content provider submits them directly. Template providers are pointed toward a single "picker" style app that hosts many clients instead.
• 4.2.1 and 4.2.7 cover narrower cases: AR apps that only drop a model into a view, and remote desktop clients.

Read the rejection message in App Store Connect carefully. It usually names the sub-clause, and the sub-clause tells you which of the problems below you are dealing with.

The five patterns that get apps rejected for minimum functionality

These are the shapes reviewers see over and over. Most rejected apps match one of them.

1. A web view around an existing site. The app loads your mobile website in a full-screen web view, with little or nothing the site itself cannot do. This is the classic 4.2 case.
2. A link hub or content feed. The app is mainly a list of articles, videos, or links that open elsewhere, which falls under the 4.2.2 language on aggregators and link collections.
3. A brochure app. Company info, a contact form, a map, maybe a promo video. Useful to you as marketing; thin to a user.
4. A template app submitted for a client. An agency or builder platform submits the app under its own account for a restaurant, gym, or event. That is the 4.2.6 case, and it is independent of how polished the app looks.
5. A single-function utility with a static screen. One page, one action, nothing that holds up past the first launch.

Note that a rejection under 4.2 is not the same as 4.3 (Spam). Spam is about duplicate or copycat apps; minimum functionality is about a single app not doing enough. The fixes differ, so do not treat them as interchangeable.

How to fix an app rejected for minimum functionality

1. Decide honestly whether the product needs to be an app

Start here, because it changes everything downstream. If the core experience is reading content or filling a form that already works well in a mobile browser, adding features just to get past review tends to produce a worse product and a repeat rejection. If there is a genuine reason users would install it, identify that reason and build the release around it.

2. Add capabilities a website cannot easily offer

Reviewers respond to things that clearly belong in an app. Depending on the product, that can include:

• Offline access to content or data the user saved
• Push notifications tied to something the user actually cares about (an order, a booking, a reply)
• Native integrations such as camera, location, Sign in with Apple, widgets, or Share extensions
• Account features that persist state: favorites, history, settings, downloads
• Native navigation and screens instead of a single web view with a browser-like toolbar

One or two capabilities that are central to the use case carry more weight than a long list of token features.

3. Remove the parts that read as a website

• Hide external links that push the user out to a browser for core tasks.
• Replace web login and checkout pages with native flows where you can.
• Make sure the app does not show website headers, footers, cookie banners, or "download our app" prompts inside itself.

4. Fix template and submission ownership (4.2.6)

If a builder or agency created the app, the fix is structural: the business that owns the content needs to submit the app from its own developer account, or the provider needs to move clients into a single multi-client app. Rebuilding the UI will not resolve a 4.2.6 rejection on its own.

5. Resubmit with a clear explanation

When you resubmit, use the notes to App Review to list what changed and where to find it. If new features sit behind a login, provide a working demo account. Reviewers who cannot reach the new functionality will often cite the same guideline again.

When to reply or appeal instead of rebuilding

If you believe the reviewer missed functionality that already exists, reply in App Store Connect and point to it specifically, with screenshots or steps. If you still disagree after that exchange, Apple offers an appeal to the App Review Board. An appeal works best when the disagreement is about facts ("the offline mode is under Settings") rather than judgment ("our app is useful enough").

How Google Play handles the same problem

Google Play has its own version, the Spam and Minimum Functionality policy, and it also targets thin wrappers around websites. The enforcement wording and process differ from Apple's, so a fix that satisfies one store does not automatically satisfy the other. For the Google Play side, see our breakdown of apps removed for spam on Google Play and the general guide to a Google Play app rejection.

If the product is really a website

Sometimes the honest answer to a 4.2 rejection is that the product works best on the web. In that case, forcing it into a store listing is not the only route. An installable web app (PWA) can be added to the home screen, and on iOS 16.4 and later, home screen web apps can receive push notifications. The trade-offs versus a native build are covered in PWA vs native app, and the no-code options are compared in how to convert a website to an app without coding. ROIBest works in this space, helping teams deliver an installable web experience alongside, or instead of, a store listing.

FAQ

What does "minimum functionality" mean in an App Store rejection?

It refers to Guideline 4.2: Apple judged that the app does not offer enough features, content, or app-like UI to go beyond a repackaged website or a simple collection of content.

Can a WebView app pass App Review?

It can if the app adds meaningful native functionality around the web content. An app that only displays an existing mobile site in a web view is the textbook 4.2 rejection.

Is Guideline 4.2 the same as 4.3 spam?

No. 4.3 targets duplicate or copycat apps and multiple versions of the same app. 4.2 targets a single app that does too little to justify being an app.

How long does review take after I resubmit?

Apple does not publish a fixed timeframe. Clear review notes and a working demo account reduce the chance of another round, which usually matters more than the queue time itself.

The short version

A minimum functionality rejection means Apple sees a website in an app wrapper, a link hub, a brochure, or a template app. Read the sub-clause, decide whether the product truly needs to be an app, add capabilities that belong to an app, fix submission ownership if a template is involved, and explain every change in your resubmission notes.