Skip to main content

Apple Guideline 4.2 and Web-Based Apps: How to Avoid Rejection

By the OnlineAppCreator editorial team4 min read

Short answer

Apple Guideline 4.2 (Minimum Functionality) rejects apps that are not sufficiently useful, unique or app-like, and it is the most common reason web-based apps fail review. WebView apps pass when they offer real functionality for a defined audience, integrate native features such as push notifications and biometrics, and behave like an app rather than a browser showing a website.

On this page
  1. What Guideline 4.2 says
  2. How reviewers apply it to web-based apps
  3. Signals that help an app pass
  4. A pre-submission checklist
  5. What to do after a 4.2 rejection
  6. Getting help with review and rejections

If you have submitted a web-based app to Apple, there is a fair chance you have seen the phrase "Guideline 4.2 - Design - Minimum Functionality" in a rejection message. It is the single most important rule for anyone packaging a Lovable, Base44, Bolt, v0 or Replit app for iOS. This article explains what the guideline actually asks for, how reviewers apply it to WebView apps, and how to respond if you are rejected.

What Guideline 4.2 says

The App Review Guidelines state that an app should include features, content and UI that elevate it beyond a repackaged website, and that apps which are not particularly useful, unique or "app-like" do not belong in the App Store. Related sub-rules address apps that are primarily marketing materials, collections of links or simple wrappers of web content. You can read the current wording in the App Review Guidelines; it changes occasionally, so check it before each major submission.

Crucially, the guideline does not ban WebViews. Many successful apps render significant parts of their interface with web technology. What Apple rejects is the experience of opening an app and finding a website that offers nothing you could not get in Safari.

How reviewers apply it to web-based apps

Reviewers spend limited time with each app. In that time they form an impression from a few signals. The most damaging are visible web behavior, such as a website header with a "Download our app" banner, links that open in Safari during core flows, pinch-zoom on text and slow page loads with a white flash. Thin content is next: a few static pages, a landing page as the start screen or a login wall with no demo account. Finally, reviewers notice the absence of anything that uses the device, such as notifications, biometrics, camera, sharing or offline handling.

Context also matters. An app for a defined audience, such as customers of a service, members of an association or employees of a company, is easier to justify than a generic content site. Apps that duplicate a large number of similar apps, for example template-based restaurant or city guides, face additional scrutiny under the spam rule in Guideline 4.3.

Signals that help an app pass

Think of passing 4.2 as accumulating evidence that the app belongs on the device. Real functionality comes first: accounts, personal data, workflows, tools or transactions that users return to. Then add native integration. A native shell like WebViewGold brings push notifications, Face ID or Touch ID login, a designed offline screen, deep links, native sharing and in-app purchases. Each of these should be connected to something meaningful in your app, not switched on for show.

Polish the web layer for touch. Remove website navigation, cookie banners and footers. Disable text zoom where layout is fixed, eliminate horizontal scrolling and make transitions fast enough that the app does not feel like a page reload. Our guide on making a WebView app feel native covers the technical side.

A pre-submission checklist

  1. Open the app cold on a real iPhone and note whether anything looks like a website within the first ten seconds.
  2. Confirm the start screen is the app's home or login, not a marketing page.
  3. Walk through every core flow and check that no step opens Safari unexpectedly.
  4. Enable and test at least two native features tied to real user value.
  5. Switch on airplane mode and check the offline experience.
  6. Create a demo account with realistic sample data for the reviewer.
  7. Write review notes that explain the app's purpose, audience and native features, with steps to reach them.

What to do after a 4.2 rejection

A rejection is not final. Read the message carefully; it often quotes the specific concern. If the reviewer misunderstood the app, reply in App Store Connect's Resolution Center with a factual explanation, screenshots or a short screen recording showing the functionality and native features. Keep the tone neutral and specific. If the concern is valid, improve the app, submit a new build and describe exactly what changed in the review notes.

If you believe the decision is wrong after a reply, you can file an appeal with the App Review Board. Appeals work best when they focus on facts: who uses the app, what it does that a website cannot, and which native capabilities it relies on. Avoid arguments based on other apps that were approved; reviewers evaluate each app on its own.

Getting help with review and rejections

Many teams lose weeks cycling through rejections because they guess what the reviewer wants. AppSubmitter provides hands-on assistance with the whole publishing process, including review notes, communication with App Review and handling rejections until the app is live. For a broader view of what goes wrong with AI-generated apps, read our overview of top App Store rejection reasons for AI-built apps, and if you are still choosing a packaging approach, compare the options in turning a Lovable project into native apps. When the right answer is a deeper native build rather than a wrapper, our custom development and company building team can take that on.

Frequently asked questions

Does Apple reject all WebView apps?

No. Apple rejects apps that feel like a repackaged website. Web-based apps with real functionality, native features and a polished touch interface are approved regularly.

Which native features help most against a 4.2 rejection?

Push notifications tied to meaningful events, biometric login, a designed offline state, deep links and native sharing are the most common. They must serve a real purpose in the app.

How long does it take to resolve a 4.2 rejection?

If a clarification in Resolution Center is enough, it can be resolved within days. If the app needs changes, the timeline depends on the work required plus another review round.

What is the difference between Guideline 4.2 and 4.3?

Guideline 4.2 concerns minimum functionality, meaning whether the app is useful and app-like. Guideline 4.3 concerns spam, meaning apps that duplicate many similar apps or are mass-produced from templates.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.