App Store Rejection 4.2: How to Get Your WebView App Approved
You submitted your app. You waited 48 hours. Then the email arrived:
Guideline 4.2 - Design - Minimum Functionality
We found that your app only includes links, images, or content that aggregates from other sources. Apps that simply wrap websites or serve as a thin veneer are not appropriate for the App Store.
If you're reading this, you probably just got rejected for Guideline 4.2. Don't panic — this is the most common rejection for web-wrapper apps, and it's usually fixable.
4.2 rejections come in a handful of shapes, and the reviewer's note almost always tells you which one you got. Here is what each shape means, and what actually clears it.
What is Guideline 4.2?
Guideline 4.2 is part of Apple's App Store Review Guidelines. The full text reads:
"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."
In plain English: Apple doesn't want the App Store filled with apps that are just WebViews loading websites. They want apps that provide value beyond what Safari can offer.
Why Apple Rejects WebView Apps
Before we talk solutions, let's understand Apple's perspective:
- User experience: Safari already exists. If your app does nothing Safari can't do, why should users download it?
- Store quality: Apple wants to curate a high-quality app ecosystem. Low-effort wrappers dilute that.
- Revenue protection: Web apps can bypass the App Store's 30% cut on in-app purchases.
- Security: WebView apps that load arbitrary content can be exploited for phishing or malware distribution.
Understanding these concerns helps you address them proactively in your submission.
7 Proven Strategies to Pass Review
Each of these answers a specific thing reviewers look for. Implement as many as apply to your app.
Add Push Notifications
MOST EFFECTIVEPush notifications are the #1 differentiator between a website and an app. Safari on iOS doesn't support web push notifications, so this is a genuine native-only feature.
Implementation requirements:
- Integrate Firebase Cloud Messaging (FCM) or Apple Push Notification service (APNs)
- Have a clear use case (order updates, messages, reminders, etc.)
- Request permission at an appropriate time, not immediately on launch
Integrate Biometric Authentication
Face ID / Touch ID is a native-only feature that dramatically improves security UX. Apple sees this as a legitimate app use case.
Add Native Navigation
Replace your web navigation with a native tab bar or navigation controller. This makes the app feel native rather than a website in a shell.
- Use a native bottom tab bar with 3-5 main sections
- Match iOS design conventions (SF Symbols, standard spacing)
- Ensure smooth transitions between tabs
Implement Offline Support
Websites are useless without internet. Apps should degrade gracefully. Even basic offline caching shows Apple you're building an app, not a bookmark.
Minimum viable offline: Cache the home screen content so users see something useful when offline, with a banner indicating limited connectivity.
Use Camera / Barcode Scanning
If your app has any use case for camera input — photo uploads, QR codes, document scanning — implement it natively rather than through web APIs.
Native camera access is faster, more reliable, and clearly "app-like."
Add a Custom App Name and Icon
This sounds obvious, but: your app should have a distinctive identity, not just your website logo slapped on a white background.
- Design a proper app icon following Apple's HIG guidelines
- Use an app name that makes sense without the .com
- Create a splash screen that matches your brand
Write a Strong App Description
Your App Store listing matters. Reviewers read it. If your description says "access our website on your phone," you're asking for a rejection.
❌ Don't write this:
"The MyBrand app lets you browse our website from your iPhone."
✅ Write this instead:
"MyBrand gives you instant notifications when your order ships, secure Face ID login, and offline access to your account — features you can't get in a browser."
Pre-Submission Checklist
Before resubmitting, verify your app has at least 3 of these features:
Appeal Template That Works
If you've made changes and want to appeal, this is the shape the reply should take — specific, itemised, and pointing at what changed:
When to Consider Web Clips
If your app genuinely has no native features to add (e.g., it's a static content site), consider using a Web Clip instead:
- Web Clips are bookmark shortcuts that appear as app icons on the home screen
- They don't require App Store approval
- They open in Safari, not a WebView, so there's no 4.2 risk
This is a legitimate alternative for informational sites that don't need app functionality.
Final Thoughts
Guideline 4.2 rejections are frustrating, but they're Apple's way of maintaining quality. The solution isn't to trick the review process — it's to genuinely add value.
Ask yourself: What can my app do that Safari can't?
If you can answer that question with 2-3 specific features, you'll likely pass review. If you can't, maybe a web clip or PWA is the right solution.
Need help passing App Review?
Code2Native includes push notifications, biometrics, and native navigation out of the box — all the features you need to pass Guideline 4.2. Start with a free build.
Code2Native Engineering
Engineering team
Written by the Code2Native engineering team — the people who build and operate the cloud build pipeline.