Minimum Functionality

4.2 is the most common rejection for AI-built apps. Reviewers open the app, see a website in a frame, and stop. The fix is changing what they see in the first two minutes, not changing the wording of your reply.

What it means

Apple thinks your app is a website in a wrapper, or too thin to justify being an app. It needs lasting, app-like value.

Common causes

• The app is mostly a WebView around a website
• No native features (notifications, offline, device capabilities, native UI)
• Template-level content or a single-screen utility

How to fix it

1. 1.Identify what a reviewer sees first. If the first screen is a scrolling web page, that is the problem.
2. 2.Add features that need the device: push notifications, offline use, camera, share sheet, widgets, Sign in with Apple.
3. 3.Render the core flow with native views, not a WebView, at least for navigation and the main task.
4. 4.Remove anything that looks like a bookmark of your site: browser chrome, cookie banners, 'visit our website' links.
5. 5.Add review notes naming the native features and how to reach them.

Usually 1 to 3 rounds to fix. Rewording alone works rarely. Arguing in the reply rarely works; the build has to show native value.

What to write to App Review

Keep it short, factual and specific. Edit the brackets to match your build.

Hello,

Thank you for the review. In the new build, [native feature 1] and [native feature 2] are available from [where]. The core flow of [task] is now built with native views. Steps to see this: [1, 2, 3].

Please let me know if you need anything else.

Independent developer, not affiliated with Apple. Guidelines change, so check Apple's current App Review Guidelines.