Google Play's policies apply to all apps on the store, including WebView apps. Most WebView apps pass review without problems, but a small number of categories and content types trigger rejection. Understanding the policies before submission saves you the time of resubmitting after a rejection.
Policies Particularly Relevant to WebView Apps
Spam and Minimum Functionality
Google Play's Spam and Minimum Functionality policy requires apps to provide value beyond simply wrapping a mobile website. In practice, this means:
- Your website must have substantial, original content: not a placeholder or a single-page marketing site with no real functionality
- The app must work correctly, navigate logically, and not crash on launch
- The app must represent its functionality accurately in its store listing
Apps with thin content (a single web page, no interactive functionality) are the most common cause of WebView app rejections. Ensure your website has a reasonable amount of content before converting it to an app.
Misleading or Impersonating Apps
Your app's name, icon, and description must accurately represent your brand and service. Apps that:
- Use names or icons similar to established brands they're not affiliated with
- Claim features in the description that don't exist in the app
- Use screenshots that don't match the actual app experience
...will be rejected under the Misleading Apps policy.
Data Safety Section
Google Play requires all apps to complete a Data Safety form in Play Console. This is separate from your privacy policy. You must accurately disclose:
- What data your app collects (location, device IDs, analytics identifiers, etc.)
- Whether data is shared with third parties
- Whether users can request deletion of their data
For WebView apps, common data to disclose:
- Analytics data from your website (Google Analytics, etc.): collected via your website, technically not the app itself, but disclose to be safe
- FCM registration token (if using push notifications): device identifier, used for notification delivery
- AdMob advertising identifier (if using AdMob)
- Location data (if your website requests location)
Privacy Policy
If your app collects any personal data (which most do, even incidentally through website analytics), a privacy policy URL is required at submission. The policy must be accessible from the app and from your Play Store listing.
Your existing website privacy policy is generally sufficient. Ensure it covers the app and mentions any app-specific data collection (FCM tokens, AdMob advertising IDs).
Content Policies
Google Play prohibits apps containing:
- Adult or explicit content (unless restricted to registered adults with age verification)
- Content related to illegal drugs
- Violent or graphic content beyond what's allowed for the declared content rating
- Hate speech targeting protected characteristics
- Content about real people that's misleading or defamatory
These policies apply to your website's content, not just app code. If your website has content in these categories, the app will be rejected.
App Content Rating
All apps must complete a content rating questionnaire in Play Console to receive an age rating (similar to PEGI or ESRB ratings for games). This rating affects who can find and install your app.
Answer the questionnaire honestly for the content on your website. Most business, blogging, restaurant, and informational apps receive an "Everyone" rating without issue.
App Review Timeline
New app submissions typically take 3–7 days for review. Updates to existing apps are usually reviewed faster, often within 24 hours. Complex reviews (apps that triggered a closer look) can take up to 30 days in rare cases.
Submit your app well before any launch date. Do not assume same-day review approval.