App-like UI
Responsive layout at 320 px and on iPad, no desktop navigation bars, no footer with 40 links, no cookie banner, no "Download our app" promo. Bottom navigation and full-width buttons help.
What the guideline actually says
Section 4.2 asks for features, content and a user interface that go beyond a repackaged website; apps that are not particularly useful or are "just a website" may be rejected. Reviewers interpret this by opening the app and asking two questions: does it feel like an app, and does it do something the mobile website cannot?
The second question is where a plain wrapper fails and a WebViewGold app passes: native push notifications, biometric login, a native offline screen, sharing through the system share sheet, QR scanning or deep links are visible, native capabilities that a Safari tab does not have.
What makes reviewers say "this is an app"
Native capability
Push notifications are the most common differentiator. Add Face ID login, native sharing, the QR scanner or offline handling and the case is clear.
Speed and completeness
Fast first paint (splash screen while loading), no dead links, no placeholder text, working forms, error states instead of blank screens.
Account hygiene
Sign in with Apple when other social logins exist, account deletion in settings, a reachable privacy policy. These are other guidelines, but a reviewer who finds them missing looks harder at 4.2 too.
A 4.2-proof setup in WebViewGold
Each step is a setting or a single JavaScript call.
Enable push notifications
OneSignal or Pushwoosh with a sensible permission prompt (ask after sign-up, not at first launch). Even one real notification type (order updates, replies, reminders) counts.
Enable the offline screen and splash
A native "You are offline" screen with retry and a splash screen until the app has loaded. Reviewers test in airplane mode.
Hide website-only elements inside the app
Use WebViewGold's custom CSS injection to remove cookie banners, app-store badges and the desktop header when the page is loaded in the app, or detect the app's user agent in your web app.
Add one native interaction
Native share sheet for sharing content, biometric lock for sensitive data, QR scanner for check-ins, haptic feedback on key actions. Pick what fits your product.
Write the review notes
Explain what the app does in two sentences, list the native features, and provide a demo account. Reviewers read these.
If you get a 4.2 rejection
Read the message: Apple names the guideline and usually describes what was missing ("the app is a thin wrapper around your website"). Reply in Resolution Center with the native features you added (be specific: "push notifications for order updates, Face ID login, offline mode"), then submit a new build. Many apps are approved on the second submission once the reviewer sees the native value.
The WebViewGold approval guarantee covers non-content rejections: if Apple rejects the app for a reason other than your content, you can claim a refund within 14 days of purchase. Our support chat helps you write the response first.
Frequently asked questions
Is a WebView app allowed in the App Store at all?
Yes. Apple's guideline 2.5.6 even requires apps that browse the web to use WebKit, which is what WKWebView and WebViewGold do. The requirement is functionality beyond a website, not a ban on web technology.
Do push notifications alone satisfy 4.2?
Often, combined with an app-like layout. Reviewers look at the whole picture; push plus offline handling plus a clean mobile UI is the usual winning combination.
My app is a dashboard behind a login. Is that a problem?
No, as long as the reviewer can log in. Provide a demo account in App Store Connect and describe what they will see.