You submitted your app and Apple came back citing Minimum Functionality. It usually means the reviewer opened your app and couldn't see why it isn't just your website. That's fixable, but rarely by changing the submission. Something in the app has to change.
What the rule says
In plain English: guideline 4.2 wants an app to be more than a repackaged website. It should be useful, feel like an app, and have some lasting value. A sub-rule, 4.2.2, also rules out apps that are mainly marketing, web clippings, content aggregators or collections of links, with catalogs as the exception.
Apple's App Review page names web-only wrappers among the things it flags.
Apple doesn't publish a list of features that count. Anyone promising that push notifications plus a splash screen guarantee a pass is guessing.
Why vibe-coded apps run into it
AI builders are very good at responsive websites, and a responsive website looks great on a phone. Then it goes in a shell, and a reviewer sees the tells:
- Web navigation: hamburger menus, full-page reloads, no back swipe
- Links that throw you out to Safari
- A blank page or a browser error with no connection
- Nothing that uses the phone
- The same thing, at the same quality, at a URL in Safari
What tends to get an app through
The question we ask is: what can someone do in the app that they couldn't do in Safari? If the answer is nothing, more polish won't help. Pick what genuinely fits the app:
- Push notifications for something people actually wait for: an order update, a reply, a reminder they asked for.
- A real offline state. Saved data where it makes sense, and a proper screen when there's no connection.
- Device features tied to the job: the camera for scanning, location for nearby results, Face ID for a private area, the share sheet for sending things on.
- Native navigation: a tab bar, back swipes, native sheets. It's often the first thing a reviewer notices.
- The app in the app. Ship your web files in the build rather than pointing at a live URL. Capacitor's docs say the live URL setting isn't meant for production, and guideline 2.5.2 bars code that changes features after review.
If you've already been rejected
- Don't resubmit the same build. You'll get the same answer, later.
- Read the message in App Store Connect. If it's unclear, reply there: Apple says that's the way to ask questions or add information.
- Make the change, then say what changed in the review notes: what to look at, where to find it, and a demo login.
- If you really think the reviewer got it wrong, you can appeal through Apple's contact form. Most of the time, changing the app is quicker.
When a wrapper is the wrong answer
If your app is mostly content, like a blog, a brochure or a list of links, adding features to get past review is working against the rule. An installable web app may serve you better. If it's complex and needs to feel native throughout, rebuilding the screens in React Native can be cheaper than patching a wrapper. Either way, you should hear that before you spend anything, and that's what our readiness report is for.
Sources
We check these before publishing. If something here has gone stale, tell us.
