App Store RejectionGuideline 4.2 — Minimum Functionality

Apple said your app is basically just a website. They're not entirely wrong.

Guideline 4.2 says your app should include features, content, and UI that elevate it beyond a repackaged website. If it mainly wraps a URL in a web view or offers one trivial function, expect this rejection.

What the rejection notice says (paraphrased)

The notice cites Guideline 4.2 and says the app doesn't offer enough features, content, or app-like functionality, for example because it mainly repackages a website. Apple asks you to add features or content that make the app useful beyond a website, then resubmit.

What this actually means

Apple wants apps to offer something a browser bookmark can't. Guideline 4.2 targets apps that aren't particularly useful, unique, or app-like, and 4.2.2 adds that apps shouldn't primarily be marketing materials, web clippings, content aggregators, or a collection of links. Web view wrappers and single-screen micro-utilities are the usual targets. Show real app value: notifications, device integrations, offline capability, or an experience that benefits from being native.

What Apple needs to see

  • Native UI components and interactions that go beyond simply rendering a website inside a web view
  • At least one meaningful feature that leverages iOS capabilities — push notifications, camera, HealthKit, Shortcuts, widgets, or offline functionality
  • A clear user benefit to having a native app rather than using a browser or Safari bookmark
  • Enough screens and features that the app represents a complete, useful experience rather than a single-function micro-utility
  1. 1Identify one or two native iOS features your users would genuinely benefit from — push notifications for updates, a home screen widget, Siri Shortcuts, or offline caching — and implement at least one of them.
  2. 2Audit your app for any screens that are purely web views rendering your own website and replace them with native SwiftUI or UIKit screens where the content is static or data-driven.
  3. 3Add a settings or profile section with native controls, as this alone demonstrates more app complexity than a bare web view wrapper.
  4. 4Write a clear description that leads with your native features so the reviewer understands immediately why this needs to be an app and not a website.
  5. 5If your app genuinely does one focused thing, make sure it does it exceptionally well — add edge case handling, customization options, and enough polish that the single function clearly warrants a native app.

While you're at it — make sure your required app pages are covered.

Fix this rejection, then make sure you're covered on the compliance side too. Every app needs a privacy policy link and a support URL, subscription apps need Terms of Use, and apps with sign-up need account deletion. A missing link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page

Common questions

My app is a simple utility — does it automatically fail 4.2?
Not automatically. A focused, well-executed single-purpose app can pass if it does something genuinely useful that benefits from native implementation. The problem is when the 'utility' is trivially simple or could just be a webpage. Quality and execution matter.
I have a WKWebView in my app but it's not the whole app. Will I get rejected?
Using a web view for specific content — like rendering rich text, a help article, or a terms page — is fine when your app has substantial native functionality around it. The rejection targets apps where the web view IS the app.
Can I appeal a 4.2 rejection?
Yes, and for 4.2 it is sometimes worth it if you believe the reviewer missed native features in your app. Write a clear, specific appeal that lists each native feature by name and tells the reviewer exactly where to find it. Keep it factual and concise.