On this page (11 sections)
What 4.2 says
The guideline asks that apps be useful, unique and “app-like”, and calls out apps that are repackaged websites, marketing material, content collections without functionality, or that provide limited value. Reviewers frequently use the phrase that the app is “not sufficiently different from a mobile browsing experience”.
WebView is not automatically banned
Apps built on WebView, Capacitor, Cordova or similar are not rejected because of the technology. They are rejected when the experience is the website with an app icon. A WebView app that adds native value — offline data, device integration, notifications that matter, camera or sensor use, a workflow that is meaningfully better as an app — can pass. A native Swift app that only shows a company brochure can fail.
Native apps can still be too limited
4.2 is about value, not build technology. Single-purpose apps with trivial functionality, apps that exist to link to other apps or websites, and apps whose only content is static text are routinely rejected regardless of how they were built.
Common triggers
- Marketing and brochure apps for a business, event or product.
- Content and link apps — articles, videos or links you could open in Safari.
- Template and app-generator output with generic screens and little custom logic.
- Apps whose main feature is elsewhere — the app is a login page to a web product.
- No standalone functionality — nothing works without visiting the website.
No-code and AI-built apps are not automatically banned. They are judged the same way: does the result provide functionality worth an app? Many do. Many are brochures.
4.2 vs 4.3
4.2 says “too little”. 4.3 says “too similar to other apps”. Template-based apps often get both: not enough functionality and identical to many others. If your message cites 4.3, read the 4.3 guide as well — the fix (meaningful differentiation) overlaps.
Why cosmetic changes usually fail
Reviewers see the new icon, the new colour scheme, the added “share” button. None of that changes what the app does. Resubmitting after a cosmetic pass typically yields the same 4.2 message with less patience behind it.
A product-value review
Answer these honestly, ideally with someone who did not build the app:
- What can a user do in this app that they cannot do on the website or in a browser?
- Which device capabilities does it use in a way that matters (camera, sensors, offline, notifications, widgets, background)?
- What would a user lose if the app were removed and only the website remained?
- Is the core value inside the app, or does the app just open the core value elsewhere?
A meaningful-feature framework
| Tends to help | Tends not to help |
|---|---|
| Offline access to data the user actually needs | A settings screen with a dark-mode toggle |
| Camera / scanning / sensors integrated into the core task | A share sheet or “rate us” prompt |
| Personalised workflows, saved state, notifications tied to user actions | A news feed of the company blog |
| Device-native interaction: widgets, shortcuts, background sync, wallet passes | A “contact us” form and a map link |
| A task that is genuinely faster or better as an app | A collection of links to other apps or sites |
Do not add random features just for review
Bolting on a calculator, a calendar or a game to a brochure app is transparent and often triggers 4.3 or 2.3 as well. Functionality should serve the user of the app, not the review.
Reply, redesign or appeal?
- Reply if the reviewer genuinely missed functionality (it was behind a login or not obvious). Explain what the app does, with screenshots or a video, and improve the review notes.
- Redesign if the honest product review says the app is thin. Build the functionality first; then resubmit with a clear description.
- Appeal only when you can point to specific, substantial functionality the reviewer did not acknowledge. Appeals that argue the app is “useful to our customers” without specifics rarely succeed.
Sometimes the website is the right product
If the value truly lives on the web, a well-built responsive site or a PWA may serve users better than an app that exists to occupy an App Store listing. We will say so when that is our assessment. It costs less than months of resubmissions.
What we can implement
Product-value assessment; native features that change the answer (offline data, device integration, notifications, workflow features) on iOS native, Flutter and React Native; and review notes that make the functionality visible to a reviewer.