Apple Guideline 4.2 and WebView Apps: How to Pass Review
Short answer: Apple Guideline 4.2 (Minimum Functionality) rejects apps that are primarily a repackaged website or lack features that make them useful as an app. WebView apps pass when they deliver an app-like experience: mobile navigation, native features such as push notifications, offline handling and device integration, and content that suits the platform. Clear review notes that point to these features help considerably.
On this page
Why does Apple reject WebView apps under Guideline 4.2?
Guideline 4.2 says an app should include features, content and UI that elevate it beyond a repackaged website. Its sub-point 4.2.2 addresses apps that are primarily marketing materials, link collections or web clippings. The guideline does not ban WebView technology. Many successful apps render significant parts of their interface with web views. What Apple rejects is an app that adds nothing a user would not get by opening Safari.
In practice, reviewers install the app, tap through the main screens and ask themselves a simple question: does this feel like an app built for iPhone, or like a website in a frame? Signals that push them toward rejection include a desktop-style layout, browser-like navigation, links that leave the app, no offline behavior and no use of device capabilities.
Typical 4.2 red flags in WebView apps
- A hamburger menu that opens a website navigation with dozens of links, including imprint and cookie settings.
- Pages that require pinch-to-zoom or horizontal scrolling.
- A white screen or browser error when the device is offline.
- External links that open inside the app without a way back, or that bounce to Safari for core tasks.
- Login screens that redirect to a web page with a different design.
- Content that is mostly static information such as opening hours, a menu or a brochure.
- No feature that uses the device: no notifications, no camera, no sharing, no biometric login.
What makes a WebView app pass
The goal is to make the native layer visibly do work. Combine app-like structure with features that only an installed app can offer. You do not need all of them; choose the ones that make sense for your users and make them obvious during review.
Then test like a reviewer. Install the release build on a clean iPhone, skip the login once, deny notifications once, switch to airplane mode and open every tab. If any of those moments shows a browser-style error or a dead end, fix it before you submit.
- Replace web navigation with a native tab bar or a compact mobile menu covering the four or five main destinations.
- Enable push notifications for events users genuinely care about, with deep links to the right screen.
- Show a branded offline screen and cache key content so the app remains useful without a connection.
- Integrate at least one relevant device feature, such as camera upload, biometric login, native sharing or location for nearby results.
- Keep users in the app for all core tasks and open truly external links in an in-app browser sheet.
- Hide web-only clutter such as cookie banners, footer link lists and desktop promotions for app users.
- Offer an account-based experience where it fits: saved items, history, personalization.
Need a hand? WebViewGold helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.
How WebViewGold helps with 4.2
WebViewGold converts websites, web apps and PWAs into native iOS and Android apps and ships the native layer that 4.2 reviewers look for out of the box: push notifications, offline and fallback modes and a native bridge with 40+ native APIs that your JavaScript can call. That means the web team can add features like biometric login, haptics, sharing or camera access without writing Swift.
Because the native bridge is called from the web code, you can also detect the app context and adapt the interface, for example hiding website footers or swapping the web menu for app navigation. WebViewGold's publishing guidance covers how to present these features to Apple reviewers.
Responding to a 4.2 rejection
A 4.2 rejection is common and recoverable. Do not resubmit the same build with a defensive message. Instead, make a visible improvement and explain it.
Reply in App Store Connect with a short, factual note listing the native features and where to find them, for example: push notifications for order updates after the first purchase, Face ID login on the second launch, offline access to saved items from the Library tab. Include a demo account with data that makes those features visible. If you believe the reviewer missed existing functionality, say so politely and point to the exact screens. If necessary, the App Review Board appeal process is available, but improving the app is usually faster than appealing.
Getting the submission right the first time
Many 4.2 rejections are partly a presentation problem: good features hidden behind a login without a demo account, screenshots that look like a website, or review notes left empty. appsubmitter.io reviews the build, listing and notes against current guidelines before submission, handles the submission inside your own Apple developer account and manages responses if a reviewer raises 4.2 or any other issue.
Combining a solid native layer from WebViewGold with a carefully prepared submission is the most reliable way to get a WebView app approved without multiple review cycles.
Frequently asked questions
Does Apple allow WebView apps at all?
Yes. Apple allows apps that use web views, and many popular apps do. Guideline 4.2 targets apps that offer little beyond a repackaged website. If your WebView app provides app-like navigation, native features such as push notifications or biometric login and a useful offline experience, it can pass review like any other app.
Which native features help most against a 4.2 rejection?
Push notifications with deep links, offline handling, biometric login, camera or file integration and native sharing are the most common and convincing. Choose features that fit your product, make them easy to discover and describe them in the review notes so the reviewer can find and test each one quickly.
Is Google Play also strict about WebView apps?
Google Play is generally less strict about the minimum functionality question, but it still rejects apps that are broken, misleading, spammy or violate its webview and content policies. A stable app with a complete data safety form, accurate listing and real user value is expected on both platforms.
How long does it take to fix a 4.2 rejection?
If your app already has native features that were not visible to the reviewer, better review notes and a demo account can resolve it within one review cycle. If native features must be added first, plan a few days to two weeks, depending on how many features you add and how quickly you can test them.
