Guideline 4.0 Design and 4.2 Minimum Functionality rejections

Guideline 4.2 (Minimum Functionality) rejects apps that are little more than a repackaged website, a collection of links, marketing material or a single piece of content, because Apple expects features, content and UI that make an app useful, unique or "app-like"; the fix is to add real native functionality, not a new wrapper.

Uptika teamPublished: November 5, 2026Last updated: November 5, 20266 min readMarkdown version

What does Guideline 4.0 Design say?

Section 4 is Apple's floor for design, not a style guide. Its introduction (App Review Guidelines, last updated October 16, 2026):

"Apple customers place a high value on products that are simple, refined, innovative, and easy to use, and that's what we want to see on the App Store. Coming up with a great design is up to you, but the following are minimum standards for approval to the App Store. And remember that even after your app has been approved, you should update your app to ensure it remains functional and engaging to new and existing customers. Apps that stop working or offer a degraded experience may be removed from the App Store at any time."

A rejection that cites 4.0 rather than a numbered part is about these minimum standards for the experience as a whole. One example Apple gives in its account deletion help: linking out to the default web browser to sign in or register "provides a poor user experience and isn't appropriate, per App Review Guideline 4."

What does Guideline 4.2 Minimum Functionality say?

4.2 asks for something an app does that a website or a file cannot. The full text:

"Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or 'app-like,' it doesn't belong on the App Store. If your App doesn't provide some sort of lasting entertainment value or adequate utility, it may not be accepted. Apps that are simply a song or movie should be submitted to the iTunes Store. Apps that are simply a book or game guide should be submitted to the Apple Books Store."

The numbered parts of 4.2 that apply to most apps:

Part	Exact text	Typical rejection
4.2.1	"Apps using ARKit should provide rich and integrated augmented reality experiences; merely dropping a model into an AR view or replaying animation is not enough."	An AR viewer that shows one 3D model
4.2.2	"Other than catalogs, apps shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links."	A brand app that lists links to the website
4.2.3(i)	"Your app should work on its own without requiring installation of another app to function."	A companion that does nothing without a second app
4.2.3(ii)	"If your app needs to download additional resources in order to function on initial launch, disclose the size of the download and prompt users before doing so."	A silent large download at first launch
4.2.6	"Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content."	A builder platform submitting client apps

4.2.6 continues: template services "should not submit apps on behalf of their clients", and a provider can instead create "a single binary to host all client content in an aggregated or 'picker' model". Template apps are also a common Guideline 4.3 spam case.

Why do webview wrapper apps get rejected?

Because a website in a frame adds nothing the browser does not already do. Apple's App Review page puts it directly: "Websites served in an iOS app, web content that is not formatted for iOS, and limited web interactions do not make a quality app." It also warns: "If your app doesn't offer much functionality or content, or only applies to a small niche market, it may not be approved."

The risks of a wrapper, in review terms:

4.2 and 4.2.2: the app is mainly web clippings or links.
4.0: web navigation, browser-style errors and pages not formatted for the screen read as a degraded experience.
2.1: a page that fails to load during review looks like an incomplete app.
3.1.1: a web checkout for digital goods inside the wrapper breaks the in-app purchase rules; see the Guideline 3.1.1 guide.
5.1.1(v): if the site has accounts, the app needs in-app account deletion; see the Guideline 5.1.1 guide.

Google Play has a parallel rule. Its spam policy does not allow apps whose primary purpose is "to provide a webview of a website without permission from the website owner or administrator", or to drive affiliate traffic to a website.

What should you check before resubmitting?

List what the app does that the mobile website cannot. If the list is empty, build those features first.
Use native navigation and screens for the core tasks; keep web content for secondary pages.
Handle no-network states with a real screen, not a browser error.
Use device features where they serve the core task, for example camera scanning, offline access, widgets or notifications people opt into.
Remove screens that are only links, promotions or a contact form.
If the app needs another app or a large download, fix 4.2.3: work on its own, show the download size and ask first.
If you build for clients from a template, submit from the content owner's account or move to one picker app.
Describe the new native features and where to find them in App Review notes and in your reply.

If your app uses a third-party or social login service to set up or authenticate the user's primary account, 4.8 requires an equivalent option from another login service that limits data collection to name and email address, lets people keep their email address private, and does not collect interactions for advertising without consent. It is not required when the app uses only your company's own account system, is an education or enterprise app using existing accounts, uses a government or industry-backed electronic ID, or is a client for a specific third-party service. Check this whenever you add social sign-in to a former web app.

When you believe the reviewer missed your features, reply first and consider an appeal only after that; the appeal guide explains the order. The rejection reasons hub covers the other guidelines.

Where Uptika fits

Uptika does not judge your app's functionality or resolve rejections. It helps you see how apps in your category present themselves and keeps your own text clean. The free Listing X-Ray reads any public listing and shows character use and three prioritized fixes, and the free Metadata Linter checks your text for policy risks before you resubmit. In the panel, Uygulama dosyası (app file) profiles any app's listing, versions and changes, and Sayfa denetimi (page audit) runs a rejection-risk check on your live listing. Start on the free plan.

Questions

What is Guideline 4.0 Design?

Section 4 sets Apple's minimum design standards for approval. Its intro says customers value products that are simple, refined, innovative and easy to use, and that apps which stop working or offer a degraded experience may be removed at any time. A rejection under section 4 can cite this intro or a numbered part such as 4.1, 4.2 or 4.3.

What is Guideline 4.2 Minimum Functionality?

4.2 says your app should include features, content and UI that elevate it beyond a repackaged website. Apps that are not particularly useful, unique or app-like, or that lack lasting entertainment value or adequate utility, may not be accepted.

Will Apple reject a webview app?

The guidelines do not ban web content as such, but an app that is mainly a website in a frame is exactly what 4.2 describes as a repackaged website. Apple's App Review page says websites served in an iOS app, web content not formatted for iOS and limited web interactions do not make a quality app.

How do I fix a 4.2 rejection?

Add functionality the website cannot offer: native navigation, offline use, device features that serve the core task, notifications people opt into, widgets, or real account features. Then describe those features and where to find them in your reply and in App Review notes.