Skip to content
← All guides

App Store

Rejected under App Store Guideline 4.2 (Minimum Functionality): what Apple rejects in wrapper and AI apps, and what to change

By Jan Lipmann, appienceChecked against sources on 8 min read

Guideline 4.2 is Apple's "this is just a website" rule. It is a judgement call, not a checklist, so no single feature guarantees approval. What you can do is remove the reasons a reviewer sees a repackaged website, add what only an installed app can do, and reply with specifics. Guideline text below is quoted from the version last updated on 2026-10-16.

App StoreCapacitorWebView

What you are seeing

The rejection arrives in App Store Connect, on the App Review page of your app. It cites Guideline 4.2 (Minimum Functionality, part of the Design section of the guidelines) and explains, in a few sentences, that the app does not offer enough beyond a website or enough lasting value. The exact wording varies by case, so read the full message rather than the notification email. Related rejections that often come with or instead of 4.2:

  • 4.2.2: the app is primarily web clippings, marketing material or a collection of links.
  • 4.3(b) Spam: the app is "indistinguishable from what's already widely available" - a thin chat screen over a public AI model is an obvious candidate.
  • 4.2.6: the app looks like it came from a commercial template or app generation service and was not submitted by the provider of its content.
  • 2.1 App Completeness: the reviewer could not get past the login screen because no demo account was provided.

How to check it yourself

Start with what Apple actually wrote. The core of Guideline 4.2:

“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.”
- App Store Review Guidelines, 4.2 Minimum Functionality

Apple's App Review page puts it more bluntly under common rejections: websites served in an iOS app do not make a quality app. Then go through your app on a real iPhone, as a reviewer would, and answer honestly:

  1. Turn on Airplane Mode and open the app. A blank white screen or a browser error page is the single most "website-like" thing a reviewer can see.
  2. Is the navigation the website's navigation - a hamburger menu, a web footer, links to "download our app" - or does it feel like an iPhone app (tab bar, back gestures, native-feeling transitions)?
  3. Does any link open your own website inside the app, or an external page with no way back?
  4. List what the app does that Safari on the same phone cannot: push notifications, camera or photo library integration, offline access, widgets, share sheet, Sign in with Apple, HealthKit or any device feature. If the list is empty, that is the 4.2 rejection in one line.
  5. Does the app load your site from a remote URL? If the binary is only a shell around https://yourapp.com, every change ships without review - and Capacitor's own docs say loading an external URL via server.url "is not intended for use in production" (Capacitor config).
  6. For AI apps: beyond sending a prompt to a model and showing the answer, what does the app do for a specific person and task? A general-purpose chat screen is what 4.3(b) calls widely available.
  7. Can a reviewer use the app at all? If it requires login, is there a working demo account in App Review Information?

Why it happens

AI builders such as Lovable produce web apps. Wrapping one in a WebView (with Capacitor or a wrapper service) is a legitimate way to ship it, but the default result is exactly what 4.2 describes: the same pages, the same navigation, nothing the installed app adds. Reviewers see the screen, not the code, so the effort that went into the product does not count unless the app shows it.

AI apps add their own risks. The guidelines have no separate "AI wrapper" rule, but several general ones apply:

  • 4.3(b): apps "indistinguishable from what's already widely available" are not accepted - a generic assistant competes with every other generic assistant.
  • 1.2 User-Generated Content explicitly covers "AI content creation apps": they need a way to filter objectionable material, a way to report content with timely responses, the ability to block abusive users, and published contact information.
  • 5.1.2(i): "You must clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so." Sending a user's text or photos to a model provider without that consent is a separate rejection waiting to happen.

How to fix it

Aim for changes a reviewer can see in the first two minutes. In rough order of impact:

Make it behave like an installed app

  • Bundle the web build inside the app instead of loading your live site. With Capacitor that means building into webDir and running npx cap sync, with no server.url in the production config.
  • Handle no network: show a native-looking offline state, and cache what the user saw last.
  • Replace web navigation with app navigation: a tab bar for the main sections, no site header or footer, no "get the app" banners, no links that open your website inside the app.
  • Handle the safe areas, the keyboard and the status bar, so nothing looks like a desktop page squeezed onto a phone.

Add something only the app can do - and make it useful

  • Push notifications for something the user actually wants to know (Capacitor's Push Notifications plugin needs the Push Notifications capability enabled in Xcode).
  • Device integration that fits the product: camera or photo picker, share sheet, widgets, haptics, biometrics to unlock, HealthKit for health apps.
  • Offline work for the core task, not just an error screen.
Note: Adding a feature the app does not need, just to have one, rarely helps. Apple's question is whether the app is useful and app-like, and a reviewer can tell a token feature from a real one.

For AI apps

  • Narrow the product: a specific job for a specific user, with its own data, history and workflow, not a general chat box.
  • Before the first request, show what data goes to which AI provider and ask for explicit permission (5.1.2(i)).
  • If users can generate or share content: filter it, add report and block actions, and publish contact details (1.2).

Clear the easy rejections at the same time

  • Demo account and notes in App Review Information (2.1).
  • If users can create an account, they must be able to delete it inside the app (5.1.1(v)).
  • If the main login is Google or another third-party login, offer an equivalent option that meets 4.8 - Sign in with Apple is the usual choice.
  • Digital features or subscriptions unlocked in the app must use in-app purchase (3.1.1). The United States storefront now allows buttons and links to other purchase methods; elsewhere they need a StoreKit External Purchase Link Entitlement, available only in specific regions (3.1.1(a)).

Reply, resubmit or appeal

You can write to App Review from the App Review page in App Store Connect before resubmitting. When you resubmit, use the Review Notes to list what changed and where to find it - a reviewer who knows where the push notifications or the offline mode are is more likely to see them. If you believe the reviewer misunderstood the app, you can appeal to the App Review Board: give specific reasons why the app complies, and note that Apple accepts one appeal per rejected submission.

When to get help

  • You have been rejected twice for 4.2 or 4.3 and are not sure what to change next.
  • The app has a deadline - a launch, a client, an investor demo - and a third rejection would miss it.
  • Adding native features means touching Swift or Xcode project settings you have not worked with.
  • You suspect the honest answer is a native rewrite of part of the app and want a second opinion before spending on it.

Sources

Primary documentation this guide was checked against. Platforms change - if something here no longer matches, the source wins.

Frequently asked questions

Does Apple reject every app built with a WebView or Capacitor?
No. Guideline 4.2 is about what the app offers, not the technology. A WebView app that bundles its content, works offline, uses device features that matter for the product and feels like an iPhone app can be approved. A WebView that only shows the website is the textbook 4.2 rejection.
Is there an App Store rule against AI wrapper apps?
Not a dedicated one. A thin chat screen over a public model usually fails 4.2 or 4.3(b) because it is indistinguishable from what is already available. AI apps must also disclose and get explicit permission before sharing personal data with third-party AI (5.1.2(i)), and AI content creation apps fall under the user-generated content rules in 1.2.
Will adding push notifications get my app approved?
Not on its own. Apple does not publish a list of features that satisfy 4.2. Push notifications help when they are genuinely useful to the user, combined with bundled content, offline handling and app-like navigation.
Should I appeal or resubmit?
If the reviewer was right that the app is close to the website, change the app and resubmit with Review Notes that point to the changes. Appeal to the App Review Board only if you believe the reviewer misunderstood the app, and give specific reasons. Apple accepts one appeal per rejected submission.

Related guides

Fixed-price audit

Want someone to check the whole app, not just this?

A review of data security, production readiness and App Store readiness for apps built with AI tools. 900 USD, a ranked list of fixes within 5 business days.