The wrapped-website syndrome

This is probably one of the most sensitive topics in App Store validation : an app that's just a website wrapped inside an app.

And honestly, plenty of projects fall into this trap.

The reasoning that sounds logical

The reasoning sounds logical : "Our website already exists, so let's just build an app around it."

Except Apple looks at something else. They ask : "Why does this experience need to exist on mobile ?" And that question changes everything.

Native mobile value

Because a mobile app brings tons of possibilities :

• notifications,
• camera,
• geolocation,
• touch interactions,
• native smoothness,
• offline mode,
• phone-optimized experience.

When an app uses almost none of that… it can quickly feel like : "This could just have been a website."

And that's exactly what triggers Apple 4.2 (Minimum Functionality) rejections. The guideline is one sentence long and leaves little room : "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." (Apple App Store Review Guidelines 4.2, 2026).

Sub-clause 4.2.2 closes the obvious workaround : "Other than catalogs, apps shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links." The key difference Apple is testing for is not how the app is built — it is whether the 7 capabilities listed above are used at all.

The problem isn't the tech, it's the value

The most important point is that the problem isn't the technology used — cross-platform frameworks pass review every day. The problem is the real mobile value. An app using 0 of the 7 native capabilities above is a browser with an icon, whatever it was written in.

Because a user doesn't necessarily download an app just to find exactly the same experience as a browser. They usually expect :

• more simplicity,
• more speed,
• more comfort,
• more mobile integration.

And honestly, many projects massively underestimate this difference.

"Why on mobile ?"

So building an app isn't just about "putting a business on a phone". It's about asking : "Why would someone want to use this service directly from their phone ?"

And that question completely changes the design, the features, the navigation, and sometimes the product model itself. In short : Apple also requires the app to stand alone — "Your app should work on its own without requiring installation of another app to function." (Apple App Store Review Guidelines 4.2.3, 2026). A wrapper that is really a shortcut to a browser fails that test twice over.

Is your project at risk of an Apple 4.2 rejection for missing mobile value ? Book a 30-minute call to turn your site into a real native app, not a wrapper.