Short answer
Guideline 4.2 rejects apps that do not offer enough beyond a repackaged website. Web-based apps pass when they deliver a focused, app-like experience with native capabilities such as push notifications, device integration and proper offline handling, and when reviewers can see that value quickly with a demo account and clear review notes.
On this page
What Guideline 4.2 actually says
Apple's App Review Guidelines section 4.2, "Minimum Functionality", asks that apps include features, content and UI that elevate them beyond a repackaged website. Sub-point 4.2.2 adds that apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or collections of links. If an app is not useful, unique or app-like, Apple considers it better suited to Safari.
Note what the guideline does not say: it does not ban web technology. Many approved apps render most of their interface with web views. The guideline judges the experience, not the implementation. That is why the same wrapping technique leads to approval for one company and rejection for another.
Why WebView apps get rejected
From the rejections we see, the triggers are remarkably consistent:
| What the reviewer sees | Why it reads as "repackaged website" |
|---|---|
| Cookie banner, website header and footer, "Download our app" prompt | It is visibly a website |
| Links opening external sites inside the app with no way back | Browser-like behaviour, broken navigation |
| No difference from visiting the URL in Safari | Nothing gained by installing |
| Marketing pages, blog posts, contact form | Content belongs on the web |
| Generic error page when offline | Not app-like |
| Login wall with no demo account | Reviewer cannot see any functionality, often a separate 2.1 rejection |
Rejections may also cite 4.2.3 or 2.1 alongside 4.2, but the root cause is usually the same: the reviewer could not see why this should be an app.
What makes a web-based app pass
Think of it as three layers, all of which should be visible within the first minute of review.
Layer 1: an app-like shell
- Remove website chrome: no site header, footer, cookie banner or app download prompts inside the app. Detect the app via user agent or a JavaScript bridge and hide them.
- Use native navigation where it helps, such as a tab bar for main sections.
- Handle external links deliberately: open them in an in-app browser sheet or Safari, never as a dead end.
- Show a designed offline screen and, where possible, cached content instead of an error page. WebViewGold ships with a configurable offline screen for this.
- Respect safe areas, dark mode and dynamic type where feasible.
Layer 2: native capabilities that serve the workflow
Choose features that make sense for your users, not a checklist for its own sake:
- Push notifications for events users care about.
- Biometric login with Face ID or Touch ID for accounts with sensitive data.
- Camera, document scanning or QR codes where users capture information.
- Native share sheet for sharing results or content.
- Local notifications and reminders, calendar or contacts integration where relevant.
- Widgets or home screen quick actions for frequent tasks.
Two or three well-integrated features usually make a stronger case than ten superficial ones.
Layer 3: focused content
Strip the app down to what users do repeatedly: the dashboard, the booking flow, the order history, the tool. Marketing pages, pricing tables and long-form content are better on the website.
How WebViewGold helps here
WebViewGold is designed around these requirements. Its iOS template loads your web app and lets you switch on native features through configuration: push notifications, Face ID, QR scanning, native sharing, offline handling, in-app purchase bridges, custom user agent for hiding web elements, and more than 40 native APIs. Because the features are native rather than emulated, they show up as genuine app functionality during review. WebViewGold also offers an approval guarantee for the App Store and Google Play with a refund if claimed within 14 days, as described on their site.
Other rules that hit web-based apps
Guideline 4.2 is the famous one, but several others regularly accompany it:
- Account deletion (5.1.1). If users can create an account in the app, they must be able to initiate deletion from within the app.
- Sign-in options (4.8). If you offer third-party social login, Apple generally requires an equivalent privacy-focused login option, such as Sign in with Apple. Check the current wording for exemptions.
- In-app purchase (3.1.1). Digital content and subscriptions unlocked in the app must generally use in-app purchase; see in-app purchases for converted web apps.
- Privacy details. Your App Store privacy labels must match what the web app and any analytics actually collect.
- Completeness (2.1). Broken links, placeholder content or a failing login lead to rejections before 4.2 is even considered.
Writing the review notes
Many rejections are avoidable with clear communication in App Store Connect:
- Provide a working demo account with realistic data, not an empty account.
- In the review notes, list the native features and where to find them ("Push: enable on first launch, test via the Notify button in Settings; QR scanner: Scan tab").
- Explain who the app is for, especially for B2B apps where the value is not obvious to an outsider.
- If the app requires specific hardware or a customer account, explain how the reviewer can still evaluate it.
If you are rejected anyway
Read the rejection carefully and reply in Resolution Center. A calm, specific response that points out native features the reviewer may have missed sometimes resolves the issue without a new build. If not, add the missing value, resubmit with improved notes and screenshots, and consider an appeal to the App Review Board for clear misunderstandings. appsubmitter.io handles exactly this kind of review communication and resubmission in your own developer account, combining AI-assisted preparation with people who have answered many 4.2 rejections.
Before you submit: a short checklist
- Website header, footer, cookie banner and app promos hidden in the app
- At least two native features that support the main workflow
- Offline screen and sensible external link handling
- In-app account deletion if sign-up exists
- Demo account and review notes that point to the native features
- Privacy labels consistent with actual data collection
For the full conversion process see converting a web app into iOS and Android apps, and for tool-specific advice, publishing a Lovable app to the App Store. Android has its own patterns, covered in Google Play rejection reasons for web apps.
FAQ
Does Apple reject all WebView apps?
No. Apple rejects apps that feel like a repackaged website. Web-based apps with focused content, app-like navigation and real native features are approved regularly.
Which native features are enough to pass Guideline 4.2?
There is no official list. Features that clearly support the main workflow, such as push notifications, biometric login, camera or QR scanning and offline handling, make the strongest case.
Can I appeal a 4.2 rejection?
Yes. Reply in Resolution Center first, then use the App Review Board appeal if you believe the reviewer misjudged the app. Usually, adding native value and clearer review notes is faster.
Does Google Play have a similar rule?
Google Play has policies against spam and minimal functionality, including apps that merely display a website. In practice it is less strict than Apple, but broken or bare WebView apps are still rejected.