Publishing Published Updated

Will Apple approve my webview app? The 2026 App Store guide

Will Apple approve my webview app? The 2026 App Store guide
TL;DR:

Yes, Apple approves webview apps, as long as they pass Guideline 4.2 on minimum functionality. That means the app has to do more than show your website. Native navigation, push notifications, biometric login, and offline screens are the usual way to get there. The app also needs to come from the business that owns the content, be built with Xcode 26 or later, include a privacy policy and privacy labels, and let users delete their account if they can create one.

Apple is generally more strict than Google about webview apps, and its rejection emails rarely say more than a guideline number. This guide covers what those numbers mean.

You get the exact wording of the guidelines that apply to webview apps, what App Review checks, the most common rejections, and how to fix them.

If you want to check everything before you submit, use our app store publishing checklist.

Key takeaways

  • Guideline 4.2 is the rule that decides most webview apps. Apple wants "features, content, and UI that elevate it beyond a repackaged website."

  • Guideline 4.2.6 says apps built from a template or app generator have to be submitted by the owner of the content, not by an agency or reseller account.

  • Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 and the iOS 26 SDK or later.

  • Apple aims to review 50% of submissions in under 24 hours and 90% in under 48 hours.

  • A demo account and clear review notes prevent a lot of avoidable rejections.

Try for free!
Enter any URL to build your app

Will Apple accept webview apps? Yes, if they pass Guideline 4.2

Yes, but provided the webview app offers an “app-like experience” with native features that go above and beyond what a simple webview app can deliver.

According to the App Store Review guidelines, “Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app isn't particularly useful, unique, or “app-like,” it doesn’t belong on the App Store.”

That quote is Guideline 4.2, Minimum Functionality. (Source: Apple, App Store Review Guidelines 4.2)

If the app has its own navigation, sends notifications, lets people log in with Face ID and handles a lost connection gracefully, you're in good shape.

Apple's official webview app policy: the guidelines that apply

Apple has no single "webview policy." Webview apps get judged under a handful of App Store Review Guidelines. These are the ones that come up. (Source for all: Apple, App Store Review Guidelines)

Guideline 4.2: Minimum functionality

The core rule. Your app needs "features, content, and UI that elevate it beyond a repackaged website." This is the guideline behind most webview rejections.

Apart from catalogs, Apple says apps shouldn't mainly be marketing materials, ads, web clippings, content aggregators, or a collection of links. A webview app that's really just your marketing site falls under this.

Guideline 4.2.6: Template and app generator apps

Apps created from a commercial template or app generation service will be rejected unless the provider of the app's content submits them directly. Publish the app under your own Apple Developer account, not your agency's or your app builder's.

Guideline 4.3: Spam

Apple rejects multiple near-identical apps from the same developer. If you run several brands or locations, Apple generally wants one app with the content inside it, not a separate app for each.

Guideline 2.5.6: WebKit

Apps that browse the web must use Apple's WebKit framework. Modern webview apps built on WKWebView, which is what Median uses, already meet this.

What App Review checks before approving a webview app

These are the checks webview apps pass or fail on most often.

1. Make your app "app-like"

Median’s Publishing Guide provides specific recommendations to help you get your app approved by Apple.

For example, to provide an "app-like" user experience we suggest you add features such as native navigation, remove any webpage footers, and design your web content so that it's scaled to display on a mobile device screen size.

Hide anything that gives the website away. That includes the site footer, cookie banners that cover the screen, "download our app" prompts and links that open Safari for core tasks.

2. Include native app features (like native plugins)

Including native plugins in your app is another way you can add native app features and improve your odds of approval.

Native plugins allow you to build a full-featured native app with a user experience that goes above and beyond displaying web content in a mobile browser.

For instance, you can send push notifications directly to your app users even when the app is in the background. It’s also easy to measure how those notifications perform, which is useful data for growth and product teams.

Median’s native plugins add features such as Face ID and Touch ID login, document scanning, and video calling without rebuilding your app. Median’s engineering team also builds custom plugins for specific native features and third-party SDKs.

Then tell the reviewer about them. Use the App Review notes in App Store Connect to list your native features and where to find them.

3. Publish under your own developer account

Guideline 4.2.6 says apps created from a template or app generation service have to be submitted by the provider of the app’s content.

The business that owns the content should publish the app from its own Apple Developer account, not from an agency’s or an app builder’s. Enrolling as an organization costs US$99 a year and requires a D-U-N-S number. (Source: Apple Developer Program enrollment)

4. Build with Xcode 26 or later

Since April 28, 2026, apps uploaded to App Store Connect have to be built with Xcode 26 and the iOS 26 SDK or later. (Source: Apple, SDK minimum requirements)

5. Privacy policy, privacy labels and account deletion

You need a privacy policy link in App Store Connect and inside the app. You also need App Privacy details, Apple’s “nutrition labels,” that match what your app and its SDKs collect.

If people can create an account in your app, they need a way to delete it from inside the app, too. That last one catches a lot of webview apps, because their delete option often only lives on the website.

6. Login and payments that follow the rules

If you offer Google or Facebook login, Guideline 4.8 asks you to also offer a login option with similar privacy protections, such as Sign in with Apple.

If you sell digital content that’s used in the app, Guideline 3.1.1 generally requires Apple’s in-app purchase, with exceptions that vary by country. Physical goods and real-world services can keep your existing checkout.

7. A working demo account and clear notes

If your app requires a login, give Apple’s App Review team a working demo account or a fully featured demo mode. Under Guideline 2.1 (App Completeness), apps must be complete and functional, with the information reviewers need to test account-based features. Make sure any required backend services are running and include instructions for features that aren’t immediately obvious.

Before you submit:

  • Enrollment fee: The Apple Developer Program costs US$99 per year. Organizations must provide a D-U-N-S Number as part of enrollment verification.

  • Review guidelines: Check the latest App Review Guidelines, particularly Guidelines 2.1, 4.2.6 and 4.8 if they apply to your app. Guideline 4.2.6 covers apps created from commercialized templates or app-generation services, while Guideline 4.8 covers login services and the requirements that may apply when third-party login is used.

  • Test on supported devices: Test your app on the iPhone and iPad models you support before submitting.

  • Preview your app: Use Median's App Studio to preview and test your app on your own device before submission.

Why Apple rejects webview apps (and how to fix each one)

Rejected under Guideline 4.2 minimum functionality

The reviewer saw your website in an app shell. Add native navigation, push notifications, and at least one device feature that fits your product. List them in the review notes and resubmit.

Rejected under Guideline 4.2.6 or 4.3

The app came from an agency or builder account, or looks like other apps from the same developer. Move it to the content owner's Apple Developer account, or combine similar apps into one.

Rejected under Guideline 2.1 app completeness

The app crashed, showed a blank screen or a broken link, or the reviewer couldn't log in. Test on a real device, check every link and add a working demo account.

Rejected under Guideline 5.1.1 privacy

Usually a missing privacy policy, privacy labels that don't match the app, or no in-app account deletion. Fix whichever one the message names.

Rejected under Guideline 3.1.1 in-app purchase

You sold digital content inside the app without Apple's in-app purchase. Add in-app purchase or move the sale outside the app where the rules allow it.

What to do if Apple rejects your webview app

  1. Read the message in App Store Connect. It names the guideline you broke.

  2. Reply in App Store Connect if something is unclear. Apple says it generally responds within 24 hours.

  3. Fix the cause, then resubmit a new build with a note on what changed.

  4. If you think the reviewer got it wrong, appeal to the App Review Board instead of resubmitting the same build.

For more rejection messages and fixes, see our guide to avoiding app store rejections.

How long does Apple take to review a webview app?

Apple says App Review aims to review at least 50% of submissions in under 24 hours and 90% in under 48 hours. Some apps take longer, especially new apps and busy periods like the weeks around a new iOS release. If you have a critical bug fix or an event deadline, you can request an expedited review, but Apple doesn't guarantee it. (Source: Apple, Request an expedited app review)

For more on timelines on both stores, read how long App Store and Google Play review takes.

How Median gets webview apps approved on the App Store

Median has turned websites into iOS and Android apps since 2014. Every app is built on WKWebView with native navigation, push notifications and access to native plugins like Face ID login, so it clears Guideline 4.2 by design. You publish under your own Apple Developer account, which keeps you on the right side of 4.2.6.

Teams use Median to skip the back and forth with App Review. Ruuster runs its app without ever touching a store submission. Conrad Siegel launched in two weeks to about 5,000 users. Read more customer stories.

  1. Do it yourself: Build and preview your app free in the App Studio, then follow our Publishing Guide to submit.

  2. Hand it off: Our App Store Publishing Service handles setup, submission, and reviewer responses for you, with a 100% approval guarantee on managed apps.

Frequently asked questions

What is the App Store webview policy?

Apple doesn’t have a separate webview policy. Webview apps are judged under the App Store Review Guidelines, mainly Guideline 4.2 on minimum functionality, which asks for “features, content, and UI that elevate it beyond a repackaged website.” Guidelines 4.2.2, 4.2.6, 4.3 and 2.5.6 also apply.

Does Apple approve every app?

No. Every app and update goes through App Review, and Apple rejects apps that break its App Store Review Guidelines. For webview apps, the most common reason is Guideline 4.2 on minimum functionality.

How can I ensure my webview app meets Apple’s “app-like” experience requirements?

For your webview app to meet Apple’s “app-like” experience criteria, tailor your web content to mobile screen sizes and add strong native navigation. Remove web-only features like webpage footers. Then list those features in your App Review notes so the reviewer can find them.

How long does Apple take to approve an app?

Apple aims to review 50% of submissions in under 24 hours and 90% in under 48 hours. New apps and busy periods, like the weeks around a new iOS release, can take longer.

Can I submit a webview app built by an agency or app builder?

Yes, as long as it’s submitted from your own Apple Developer account. Guideline 4.2.6 says apps made from templates or app generators have to be submitted by the content owner.

What version of Xcode do I need to submit an iOS app in 2026?

You need Xcode 26 with the iOS 26 SDK or later. Apple has required it for all uploads to App Store Connect since April 28, 2026.

How can I convert my website to an app that complies with Apple’s guidelines?

To convert your website into an app that meets Apple’s guidelines, make sure the iOS webview app offers more than a mobile version of your website. It should include app-specific features like push notifications, access to device hardware and a design optimized for mobile. It also needs to add value through user engagement and smooth interaction that fits the native iOS experience. You can build and preview your app for free in the Median App Studio.

What is an App Store publishing service?

An App Store publishing service helps you through the submission process and makes sure your app meets Apple’s guidelines. It can also help with your app marketing strategy, app optimization and maintenance after approval. These services cover everything from the first submission to handling rejections and updates, and costs vary with the level of help you need. Learn more about Median’s App Store Publishing Service.

Can I create an e-commerce webview app for my Shopify site?

Yes. Shopify stores sell physical goods, so your existing checkout works without Apple’s in-app purchase. Add push notifications for drops and abandoned carts, plus native navigation, so the app clears Guideline 4.2.

Will Google Play approve my webview app?

Yes, with conditions. Google Play is generally less strict than Apple, but it rejects apps that only mirror a website and requires builds that target API level 36. Read will Google Play approve my webview app for the full checklist.

*DISCLAIMER: This content is provided solely for informational purposes. It is not exhaustive and may not be relevant for your requirements. While we have obtained and compiled this information from sources we believe to be reliable, we cannot and do not guarantee its accuracy. This content is not to be considered professional advice and does not form a professional relationship of any kind between you and GoNative.io LLC or its affiliates. Median.co is the industry-leading end-to-end solution for developing, publishing, and maintaining native mobile apps for iOS and Android powered by web content. When considering any technology vendor we recommend that you conduct detailed research and "read the fine print" before using their services.*

Build better apps, faster. It's never been easier.