# Guideline 4.2 Minimum Functionality rejection > Rejected under Guideline 4.2 because the app is “not sufficiently different from a mobile browsing experience”? What to add, and a reply for App Review. **Guideline 4.2 — Minimum Functionality: it looks like a website in an app.** The reviewer found nothing the app does that your website doesn’t already do in Safari. Wrapped web apps get this when they show the same pages, keep desktop navigation, load the live site, or send people out to the browser. - App Store · Guideline 4.2. Minimum Functionality: it looks like a website in an app. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## What this rejection means The reviewer found nothing the app does that your website doesn’t already do in Safari. Wrapped web apps get this when they show the same pages, keep desktop navigation, load the live site, or send people out to the browser. ## Why reviewers send it An App Store app is supposed to be worth installing. When the reviewer can do everything in Safari — same pages, same navigation, links that open the browser — the wrapper adds nothing, and that is exactly what 4.2 rejects. It is the usual reason wrapped Lovable, Bolt and Base44 apps are rejected. ## The message App Review sends ``` Guideline 4.2 - Design - Minimum Functionality We found that the usefulness of your app is limited by the minimal functionality it currently provides. Your app provides a limited user experience as it is not sufficiently different from a mobile browsing experience. ``` The exact wording changes from one review to the next; the guideline number is what to look for. ## How to fix it 1. Add one or two things a browser can’t do well, in the main flow: push notifications, camera capture, the share sheet, haptics, offline data. 2. Make it feel like an app: bottom tabs, safe areas around the notch, no hover-only menus, no website footer or “open in browser” banner. 3. Keep sign-in and payments inside the app instead of bouncing to Safari. 4. Bundle the web build in the app rather than loading your live site with server.url. 5. In the reply, tell the reviewer where each new feature is. Before you resubmit, run the [Guideline 4.2 self-audit](https://capwr.app/free-tools/apple-guideline-4-2): six questions on what reviewers look for in a wrapped web app. ## Fix it with Lovable, Bolt or Cursor If the app was built with an AI builder, paste this into it, then check the result on a phone: ``` Make the app feel native on iPhone: bottom tab navigation, safe-area padding, no website header, footer or “open in browser” links. Add [push notifications / camera capture / the share sheet] with the matching Capacitor plugin where it fits the main flow. ``` ## What to reply in App Store Connect Replace the [brackets] with what you actually changed: ``` Guideline 4.2 — We have added features that make [App name] more than a website: [feature 1, e.g. push reminders] and [feature 2, e.g. camera capture]. You can find them under [tab or screen]. Navigation now uses native tab bars, and [what] works offline. ``` ## Got a different message? Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded. ## Other App Store rejections - [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple) - [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)