# Google Play webview and minimum functionality

> Google Play rejected the app under Spam and Minimum Functionality for being a webview of a website? What to add, and when you need permission.

**Spam and Minimum Functionality — Minimum Functionality: a webview of a website.** Google sees an app that mostly shows a website, with little added for people who install it — Google Play’s version of Apple’s 4.2. Wrapping a site you don’t own needs the owner’s permission.

- Google Play · Spam and Minimum Functionality. Minimum Functionality: a webview of a website.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/google-play-webview-minimum-functionality
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## What this rejection means

Google sees an app that mostly shows a website, with little added for people who install it — Google Play’s version of Apple’s 4.2. Wrapping a site you don’t own needs the owner’s permission.

## Why reviewers send it

Google Play doesn’t want apps that only frame a website, and forbids webviews of sites the developer doesn’t own without permission. It is the Play version of Apple’s Guideline 4.2, and it hits wrapped web apps the same way.

## The message Google Play sends

```
Issue found: Violation of Spam and Minimum Functionality policy

Your app provides a limited user experience: it appears to be a webview of a website, without adding significant value or functionality for users.
```

The exact wording changes from one review to the next; the policy name is what to look for.

## How to fix it

1. Bundle the web build in the app instead of loading your live site, and add app-only value: notifications, offline data, camera or share features.
2. Remove website chrome: cookie banners, desktop menus, footers and “download our app” prompts.
3. If the site isn’t yours, get written permission from its owner, or don’t publish it.
4. Upload a new build, then resubmit or appeal with a description of the changes.

Before you resubmit, run the [Guideline 4.2 self-audit](https://capwr.app/free-tools/apple-guideline-4-2): six questions on what reviewers look for in a wrapped web app.

## Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

```
Make the app feel native on Android: bottom navigation, no website header, footer or cookie banner, and add [push notifications / camera capture / sharing] with the matching Capacitor plugin.
```

## What to tell Google Play

Replace the [brackets] with what you actually changed:

```
The app now offers [features] that the website doesn’t, ships its interface inside the app, and [what] works offline. We own [domain].
```

## Got a different message?

Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded.

## Other Google Play rejections

- [Google Play Broken Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-broken-functionality)
- [Google Play invalid privacy policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-invalid-privacy-policy)
- [Google Play Data safety section inaccurate](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-data-safety-inaccurate)
- [Google Play missing login credentials](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-missing-login-credentials)
- [Google Play account deletion requirement](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-account-deletion)
- [Google Play photo and video permissions policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-photo-video-permissions)
- [Google Play Payments policy: use Play Billing](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-payments-policy)
- [Google Play Metadata policy violation](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-metadata-policy)
- [Google Play production access refused](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-production-access-denied)

## Fixed it? Ship the new build to Google Play

CapWrapp builds and signs the Android app from your GitHub repo, bumps the version code, and uploads it to Google Play — then promotes it to production when you are ready.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)