How to Get Your WebView App Approved on Google Play in 2026

Google Play rejected 1.75 million app submissions in 2025 alone. WebView apps are among the most scrutinized categories. If you've had your app rejected — or want to avoid it — this guide covers every policy you need to know.

Why Google Rejects WebView Apps

Google's policies target WebView apps specifically under two categories:

1. Webviews and Affiliate Spam Policy

Google does not allow apps whose primary purpose is to drive affiliate traffic to a website or simply provide a WebView of a website without permission from the site owner. This is the #1 reason WebView apps get rejected.

• You must be the owner or have written authorization from the website owner
• Keep proof of ownership ready (domain registration, signed agreement)
• If Google asks, you can submit documentation via their Advance Notice Form

2. Minimum Functionality Policy (Updated August 2024)

Your app must offer a "stable, responsive, and engaging user experience." Apps that merely mirror website content without app-like enhancements will be rejected. Google specifically looks for:

• Does the app crash, freeze, or show rendering errors?
• Does it offer something a mobile browser can't?
• Is the content unique, or does it duplicate other Play Store apps?

The Approval Checklist (2026 Requirements)

Follow every item on this list before submitting:

Technical requirements

1. Use AAB format, not APK: Google requires Android App Bundle (.aab) for all new apps. APKs are no longer accepted for new submissions.
2. Target API level 35 (Android 15): As of August 31, 2025, new apps and updates must target Android 15. This is enforced.
3. Use Play Integrity API: Replace the deprecated SafetyNet Attestation API with Play Integrity for app verification.
4. Google Play Billing Library v7+: If your app has any in-app purchases, use the latest billing library.

Content and functionality requirements

1. Add at least 2-3 native features beyond basic WebView browsing:
   • Push notifications (Firebase Cloud Messaging)
   • Native navigation bar (bottom tabs)
   • Splash screen with your branding
   • Offline fallback screen
   • Biometric authentication
2. Privacy policy: Must be accessible from within the app AND on your store listing. It must clearly describe what data you collect.
3. Data Safety form: Complete it accurately in Google Play Console. Declare everything — cookies, analytics, crash reports.
4. Account deletion: If your app allows account creation, you must offer in-app account deletion.

Store listing requirements

1. Accurate screenshots: Show what your app actually looks like. Don't use mockups that misrepresent the experience.
2. Honest description: Don't claim features you don't have. Avoid superlatives like "best" or "fastest" without evidence.
3. Proper categorization: Choose the right category. A news reader shouldn't be in "Tools."
4. Content rating: Complete the IARC questionnaire truthfully.

New Developer Account Requirements

If you're creating a new Google Play developer account in 2026, be aware of these additional steps:

• Identity verification: Google may require government ID or business documents.
• Closed testing requirement: New apps must complete 14 days of closed testing with at least 20 testers before going to production.
• $25 one-time registration fee.

Common Rejection Reasons and How to Fix Them

Rejection: "Webviews and Affiliate Spam"

What it means:

Google thinks your app is just wrapping someone else's site for profit.

How to fix:

• Prove you own the website (WHOIS records, DNS TXT verification)
• Add native features that go beyond simple browsing
• Submit an appeal with documentation via Google Play Console

Rejection: "Minimum Functionality"

What it means:

Your app doesn't do enough to justify being an app instead of a bookmark.

How to fix:

• Integrate push notifications (even if basic)
• Add a native bottom navigation bar
• Implement an offline fallback page
• Enable biometric login or remember-me functionality

Rejection: "Data Safety Issues"

What it means:

Your Data Safety declaration doesn't match what your app actually does.

How to fix:

• Audit all SDKs in your app (Firebase, OneSignal, analytics) for data collection
• Update the Data Safety form to accurately reflect ALL data types
• Ensure your privacy policy URL is valid and loads correctly

How Code2Native Handles All of This

Our build engine automatically handles most of the technical requirements:

• AAB format: All Android builds output .aab files by default
• Target API level: Always targets the latest required API level
• Native features: Push notifications, bottom tabs, splash screen, and offline fallback are built-in
• Permissions: Only requests permissions your app actually uses

You still need to handle the store listing, privacy policy, and Data Safety form yourself — but the app itself will meet Google's technical standards.

FAQ

Can a WebView app actually get approved on Google Play?

Yes. Thousands of WebView-based apps are live on Google Play. The key is adding genuine native functionality beyond simple web browsing. Services like Median.co, Natively, and Code2Native exist specifically because this approach works when done correctly.

How long does Google Play review take?

For new apps: 2-7 business days. For updates to existing apps: usually 1-3 days. New developer accounts take longer due to the 14-day closed testing requirement.

What if my app gets rejected? Can I resubmit?

Yes. Fix the issues mentioned in the rejection email, then resubmit. There's no penalty for resubmission. If you disagree with the rejection, you can file an appeal through Google Play Console.

Do I need to target API level 35 right now?

Yes, since August 31, 2025, all new apps and updates must target API level 35 (Android 15). Existing apps that stop updating may eventually be hidden from search results on newer devices.