Publishing Published Updated

Will Google Play approve my webview app? The 2026 policy guide

Will Google Play approve my webview app? The 2026 policy guide
TL;DR:

Yes. Google Play approves webview apps every day. It rejects the ones that only mirror a website, crash or freeze, or wrap a site the developer doesn't own. To get approved in 2026, your app needs native app features, a build that targets Android 16 (API level 36), an Android App Bundle, a privacy policy and a completed Data safety form. New personal developer accounts also need a 14-day closed test with at least 12 testers before they can publish.

Most webview rejections come down to two things. Either the app doesn't do anything the website can't, or the build misses a technical requirement Google changed this year. This guide covers both. You get the exact policy wording Google uses, the seven checks your app has to pass, the most common rejection reasons, and how to fix each one. If you'd rather check everything before you submit, use our app store publishing checklist.

Try for free!
Enter any URL to build your app

Key takeaways

  • Google Play doesn't ban webview apps. Its Spam policy bans webview apps whose main purpose is to show a website without the owner's permission or to drive affiliate traffic.

  • Its Functionality policy rejects apps with limited content or function and apps that crash, freeze, or won't load.

  • Since August 31, 2026, new apps and updates must target Android 16 (API level 36). You can request an extension to November 1, 2026.

  • Native features such as push notifications, biometric login, offline screens, and native navigation are what make a webview app feel like an app to reviewers and users.

  • If you sell digital goods used inside the app, plan for Google Play Billing before you submit.

Will Google Play accept webview apps? Yes, with conditions

Yes. Plenty of apps on Google Play load some or all of their screens in a webview, from retailers to banks to SaaS dashboards. Google focuses on whether the app works, whether you have the right to publish the content, and whether users get enough value to justify installing it.

When a reviewer opens your app, they assess whether it offers enough functionality and value beyond simply displaying a website. Apps that fall short may be rejected under Google Play’s Spam or Functionality policy.

Google Play's official webview app policy (2026)

Google doesn't have a policy called "the webview policy." Webview apps get judged under two sections of the Google Play Developer Program Policies. Here's what each one says.

The Spam policy on webview apps

Under "Webviews and Affiliate Spam," Google says it doesn't allow apps whose primary purpose is to drive affiliate traffic to a website or to provide a webview of a website without permission from the website's owner or administrator. Google's own example of a violation is an app that does nothing but load Google Shopping in a webview. (Source: Google Play Console Help, Spam)

So if the website is yours, this part of the policy is on your side. If it isn't, get written permission from the owner before you submit.

The minimum functionality policy for webview apps

Google's Functionality, Content, and User Experience policy says, "We do not allow apps that only have limited functionality and content." The examples it lists include static apps with only text or PDF files, apps with very little content, and apps that do nothing. (Source: Google Play Console Help, Functionality, Content, and User Experience)

The same policy covers broken apps. "We don't allow apps that crash, force close, freeze, or otherwise function abnormally." That includes apps that won't install, won't load, or load but don't respond.

Google has been direct about where webview apps land. In a policy guide for developers, it says webview apps built mainly to drive traffic "rather than providing engaging app experiences" are considered webview spam and removed from Play. (Source: Android Developers Blog)

Definition of a webview app: A webview app is an Android app that shows web content inside the app using Android's WebView component, often alongside native screens and device features. For the longer version, read what is a webview app.

What Google Play checks before approving a webview app

Reviewers look at the same things for every app. For webview apps, these seven are where things go wrong.

1. App features beyond your website

Give people a reason to install. Push notifications, biometric login with Face ID style fingerprint or face unlock, a native tab bar or side menu, an offline screen, camera or file uploads, and deep links all show the reviewer this is an app. You don't need all of them. Two or three that fit how your customers use you is usually enough.

2. Permission to publish the website

Wrap your own site, or get written permission from the owner. Make sure the developer name on your Play Console account matches the business behind the website, so the reviewer can connect the two.

3. Google Play target API level requirements

Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher. Existing apps must target Android 15 (API level 35) or higher to stay visible to new users on newer Android versions. If you need more time, you can request an extension to November 1, 2026 in Play Console. (Source: Android Developers, Meet Google Play's target API level requirement)

4. An Android App Bundle (AAB), not an APK

New apps on Google Play must be published as an Android App Bundle. You can still build an APK to test on your own phone, but Play Console wants the AAB. (Source: Android Developers, About Android App Bundles)

5. A privacy policy and a completed Data safety form

Every app needs a privacy policy at a public link and a Data safety section in Play Console. What you declare has to match what the app actually does, including data collected by any SDKs you add for push, analytics, or ads. (Source: Google Play Console Help, Data safety section)

6. Closed testing for new personal developer accounts

If you opened a personal Play Console account after November 13, 2023, you need to run a closed test with at least 12 testers who stay opted in for 14 days in a row before you can apply for production access. Organization accounts don't have this step. (Source: Google Play Console Help, App testing requirements for new personal developer accounts)

7. Developer verification

Google is rolling out Android developer verification. As of September 30, 2026, apps installed on certified devices in Brazil, Indonesia, Singapore and Thailand must come from verified developers, with a global rollout planned for 2027. Play Console developers verify through their account. Read our guide to Android developer verification for what to prepare.

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

Here's what the rejection usually says, what it means, and what to change.

Rejected for minimum functionality or webview spam

The reviewer saw your website in a frame and nothing else. Add native navigation, push notifications, and at least one device feature that fits your product. Remove browser-like elements that give it away, such as a visible URL bar, or links that jump out to Chrome for core tasks.

Rejected for broken functionality

The app crashed, showed a blank screen or got stuck. Test on a real Android phone or Median's browser-based simulator in the App Studio before you submit.

Check the back button, logins, file uploads, external links, and what happens with no signal. Add an offline screen so the reviewer never sees a browser error page.

Rejected for a missing privacy policy or Data safety mismatch

Open your privacy policy link in a private window to make sure it loads. Then go through your Data safety form again and compare it with every SDK in the app.

Upload blocked for target API level

This isn't a review rejection. Play Console won't accept the upload at all. Rebuild targeting API level 36, or request the extension if you need until November 1, 2026.

Rejected for payments

You sold digital content inside the app without Google Play Billing. See the payments section below.

Rejected for metadata or impersonation

Your screenshots, icon, or description don't match the app, or you used a brand you don't own. Use real screenshots from the app and publish under the business that owns the site.

What to do if Google Play rejects your webview app

  1. Read the email and Play Console's Policy status page. Both name the policy you broke.

  2. Fix the cause, not the wording. Resubmitting the same build with a new description rarely works.

  3. Submit a new build with a higher version code and a short note to the reviewer about what changed.

  4. If you think the reviewer got it wrong, file an appeal from Play Console instead of resubmitting.

For a deeper walkthrough with real rejection messages, see our guide to avoiding app store rejections and how to fix them.

Selling digital goods in a webview app? Plan for Google Play Billing

If your app sells digital goods or subscriptions used inside the app, Google's Payments policy generally requires Google Play Billing, with some regional exceptions.

Physical products, such as a Shopify store, and services used outside the app, like bookings or deliveries, can keep your existing checkout. (Source: Google Play Console Help, Payments)

Median's in-app purchase plugin connects Google Play Billing to your web checkout so you don't have to rebuild it.

Webview security settings that keep reviewers happy

Google Play reviewers don’t read your code line by line. They do run automated checks on every build, and a few webview settings show up in those checks again and again.

Get these right and you remove an easy reason for a warning or rejection.

Enabling safe browsing

Safe Browsing has been on by default in Android WebView since WebView 66.

When someone taps a link to a known phishing or malware site inside your app, WebView shows a warning page instead of loading it. On Android 8.0 (API level 26) and up, you can also turn it on or off for a single WebView with setSafeBrowsingEnabled().

You can turn Safe Browsing off for the whole app by setting android.webkit.WebView.EnableSafeBrowsing to false in your manifest. In a public app there’s rarely a good reason to, so leave it on unless you have a specific technical need.

Handle SSL errors the safe way

Some apps, or the libraries they use, tell WebView to ignore SSL certificate errors so pages load no matter what. Google flags that as an unsafe implementation of onReceivedSslError because it leaves the app open to man-in-the-middle attacks, where someone on the same network can read logins or change what loads in your app.

Google’s fix is simple. Only call proceed() when the certificate is one you expect, and call cancel() for everything else. If you get the warning and the code came from a third-party library, contact the provider.

Google says apps that leave the issue unfixed past the Play Console deadline can be removed from Google Play. (Source: Google Help, Remediation for unsafe implementation of WebViewClient.onReceivedSslError)

Permissions and content access

Every permission your app uses has to be listed in the AndroidManifest.xml file. Internet access is a normal permission, so Android grants it automatically. Permissions like camera, location and contacts are different. Android asks the user at runtime, and Google Play looks at whether your app really needs them.

Only ask for the permissions your app actually uses. If you request the camera, location, or contacts, the reviewer expects to see a feature that needs them, and your Data safety form needs to say so.

Photos and files work the same way. Most webview apps only need users to upload an image or a document now and then, and Google wants those apps to use the system photo picker instead of asking for broad access to the photo library. Since May 28, 2025, apps that request READ_MEDIA_IMAGES or READ_MEDIA_VIDEO without a core need for them have had to remove those permissions or file a declaration in Play Console explaining why a picker won’t work. (Source: Google Play Console Help, Photo and Video Permissions policy)

How Median gets webview apps approved on Google Play

Median has turned websites into Android and iOS apps since 2014. Every build covers the checks above by default. It targets the current API level, ships as an AAB, and adds the native features reviewers look for, including push notifications, biometric login, native navigation, and offline screens. You keep running your website, and the app updates when your site does.

Teams use it to skip the back and forth with reviewers. 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.

There are two ways to start:

  1. Do it yourself. Build and preview your app free in the App Studio, then pay once to build and publish under your own developer accounts.

  2. Hand it off. Our Publishing Service handles store setup, submission, and review responses for you. On the Business plan, the Median team also keeps your app updated ahead of every Android and iOS release.

Frequently asked questions

What is Android webview used for?

Android System WebView is a component Google pre-installs on Android phones. It lets apps show web pages inside the app instead of opening a browser. Webview apps use it to load web content while native code handles navigation, notifications and device features.

Will Google Play approve a website converted to an app?

Yes, if the app adds something the website doesn't and meets the technical requirements. Google rejects converted websites that only mirror the site, so add native features such as push notifications, biometric login, and native navigation, and build for API level 36 as an AAB.

What target API level does Google Play require in 2026?

Since August 31, 2026, new apps and updates must target Android 16 (API level 36). Existing apps need Android 15 (API level 35) to stay available to new users on newer Android versions. You can request an extension to November 1, 2026.

Can I publish a webview of a website I don't own?

Only with permission from the owner or administrator. Google's Spam policy bans apps whose main purpose is to show someone else's website in a webview without permission.

Do I need 12 testers to publish on Google Play?

Only if you have a personal developer account created after November 13, 2023. You need at least 12 testers opted in to a closed test for 14 days in a row. Organization accounts skip this step.

How long does Google Play review take?

Google says reviews can take up to seven days and sometimes longer, especially for new developer accounts. Plan your launch date with that buffer in mind.

Will Apple approve my webview app too?

Apple is stricter. Its Guideline 4.2 asks for features beyond a repackaged website. Read will Apple approve my webview app for the iOS version of this guide.

Can I create an Android webview app for my Shopify store?

Yes. Shopify stores sell physical goods, so your existing checkout works and you don't need Google Play Billing. Add push notifications for drops and abandoned carts, plus native navigation, so the app does more than the mobile site.

How do I get my webview app approved on Google Play the first time?

Wrap a site you own, add two or three native features, target API level 36, upload an AAB, link a working privacy policy and fill in the Data safety form to match your SDKs. Test on a real phone first. Our app store publishing checklist covers every step.

*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.