Lorixen.
EN

Rejected as a Website in a Wrapper? What Apple Means by Minimum Functionality

Short answer: Apple's guidelines say an app should include features, content and a user interface that lift it beyond a repackaged website. If your submission is essentially your site inside a web view, with the same menus, the same pages and nothing that needs a phone to work, expect a 4.2 rejection. The usual cure is not a redesign. It is adding a few things that a phone does better than a browser, and making the app feel like a place people return to rather than a bookmark with an icon.

What the reviewer sees

A reviewer opens your app and asks one question: why is this not just a link on the home screen? If the answer is visible within a minute, you pass. If the first screen is a browser address bar's worth of content, with desktop-width layouts, cookie banners and links that bounce out to Safari, the answer is "it is a link".

Common triggers:

  • The whole app is one web view loading your homepage
  • Navigation is the website's own header menu, not app navigation
  • Tapping most things opens an external browser
  • The app has no reason to exist offline, on a lock screen or with the camera
  • A marketing brochure, with no account, no task and no state

None of this means web technology is banned. Many good apps use web views for parts of a screen, such as a terms page or a receipt. The problem is when web content is the whole product.

Common mistakes and fixes

Mistake 1: One web view, no native shell

Fix: Build native navigation, such as a tab bar with three to five destinations, and give each destination purpose. A café might use Order, Rewards, Find Us. Each can still load some web content, but the structure belongs to the app.

Mistake 2: Nothing that needs the device

Fix: Add one or two features that rely on the phone. For a small business, sensible ones include:

  • Camera or photo upload tied to a task, such as attaching a photo to a repair request
  • Push notifications for order status, with the user's consent
  • Biometric sign-in for returning customers
  • Saving a booking to the phone's calendar
  • A scan feature for loyalty cards or tickets

Pick features that serve a real job. Bolting on a random flashlight button counts for nothing.

Mistake 3: A brochure with a download button

Fix: Give the app a task loop. A person opens it to do something: reorder, check a job, see a balance, book a slot. If the honest purpose is "read about us", the website already does that and an app is the wrong format.

Mistake 4: Desktop pages squeezed into a phone

Fix: Check touch targets, text size and horizontal scrolling. A page that needs pinch-zoom screams "website". Use layouts designed for the narrow screen and respect safe areas around the notch and home indicator.

Mistake 5: Links that leave the app

Fix: Keep common journeys inside. External links should be the exception, such as a privacy policy. If your checkout lives on a separate site, consider an in-app flow, bearing in mind Apple's separate rules about payments for digital goods and services.

Mistake 6: Broken or empty states

Fix: Handle no network, slow network and signed-out users with real screens. An app that shows a white page offline fails the "feels like an app" test quickly.

A decision table: wrap, hybrid or native?

Your situation Sensible route
Content-heavy site, few interactions Keep it as a website, add a home-screen web app option
Existing web app with accounts and tasks Hybrid: native shell plus web screens, with device features added
Heavy camera, offline or hardware use Mostly native screens
Tight budget, one skilled developer Cross-platform framework with native navigation, as long as it feels native

A hybrid approach is common and acceptable. What matters is the result, not the technology label.

A short plan to fix a 4.2 rejection

  1. Read the message. Reviewers write which guideline they applied and sometimes name the symptom. Reply in the Resolution Center if something is unclear.
  2. List what is native today. Be blunt. If the list is empty, that is your finding.
  3. Choose two or three improvements from the feature list above. More is not better.
  4. Rebuild navigation so the app has its own structure.
  5. Write review notes that describe the native features and tell the reviewer where to find them. A reviewer who cannot find the feature assumes it is absent.
  6. Test on a clean device with a poor connection.
  7. Resubmit with a short, factual summary of what changed.

Illustrative example: a fictional dog-grooming business submits its booking site wrapped as an app and is rejected. In the second version, it adds a tab bar, lets owners upload a photo of their dog's coat before a booking, sends a reminder notification the evening before, and adds the booking to the phone calendar. Same booking engine underneath, but the app now does something the site cannot do as well.

Things Apple may still ask about

Even with strong features, other guidelines apply. Account sign-in may trigger the requirement to offer in-app account deletion. Collected data needs matching privacy labels. If you sell digital items in-app, payment rules apply. A 4.2 rejection is often the first of several questions, so check your submission against the whole guideline list rather than assuming one fix is the end.

Should you appeal?

You can, but think before doing so. An appeal makes sense when the reviewer misread your app, for instance when it has plenty of native features that were not visible because the demo account lacked data. It makes little sense when the app really is a website in a frame. In the second case, improving the app is faster than arguing.

FAQ

Is using a web view always a problem?

No. Web views are normal for parts of an app. The risk is an app with nothing else.

Does Google Play have the same rule?

Google Play has its own quality and spam policies and is generally less strict about web content, but it does not welcome apps that exist only to redirect or mislead. Check its current policy text before relying on that.

Will a progressive web app do instead?

For many content-led businesses, yes. A web app added to the home screen costs less and avoids store review altogether. The trade-off is fewer device features and no store listing.

How many native features are enough?

Apple does not publish a number. Aim for an app whose value is clear within a minute of opening it.

If your submission has been rejected under this rule, send us the rejection message and we will tell you what to add before you resubmit.

Sources

WhatsAppBook a call