Convert WeWeb to an Android App: Google Play Guide (2026)

Key takeaways

WeWeb has no Google Play export. Package the published app either as a WebView app with native modules or as a Trusted Web Activity built on WeWeb's PWA settings.
A TWA only runs without browser UI when /.well-known/assetlinks.json verifies your domain – and WeWeb developers have reported trouble serving that file, so test the path first.
New personal Play Console accounts need 12 testers opted in for 14 days; every app needs an AAB targeting API 36, Data safety answers and in-app plus web account deletion.
WebViewGold for Android, made by our team, adds push via OneSignal, Firebase or Pushwoosh, App Links, biometrics, scanners and Play Billing; appsubmitter.io runs the Play Console side.

Our recommended solution

Turn your WeWeb app into a real Android app with WebViewGold

WebViewGold wraps the WeWeb web app you already have in a native Android Studio project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at Google Play look for. Built by our own team, and we submit WebViewGold apps all the time.

Get WebViewGold How it helps ↓

Can you convert a WeWeb app into an Android app?

Yes. You convert WeWeb to an Android app by packaging its published URL in a native Android shell – a WebView app or a Trusted Web Activity – building an Android App Bundle and releasing it through Google Play Console. As of October 2026, WeWeb doesn't publish to Google Play itself, so the packaging, the Play Console setup and the policy declarations are on your side.

Android is friendlier to web apps than iOS in one respect: Chrome lets people install a progressive web app, and WeWeb's PWA settings (app name, icon, theme and background color, display mode) plus optional custom /manifest.json and /serviceworker.js files give you a solid base. WeWeb's legacy PWA plugin even offers vibration on Android only, citing an iOS limitation. But an installed PWA isn't a Google Play listing. For that you need an app package – and with it come Google Play's policies.

WeWeb's own stance hasn't moved since 2024: staff said the PWA plugin wouldn't include store publishing and that native apps weren't a priority. Community threads mention PWABuilder, Capacitor, Expo and webtonative; treat them as community suggestions, not as WeWeb recommendations. If you want the iPhone version too, our guide to converting WeWeb to an iOS app covers Apple's side.

WebView app or Trusted Web Activity for a WeWeb project?

Question	WebView app (for example WebViewGold)	Trusted Web Activity (for example Bubblewrap or PWABuilder)
Who renders WeWeb?	Android System WebView inside your app	The user's browser, usually Chrome, in full screen
What do you need first?	Your production URL	A PWA that meets the install criteria, plus verified Digital Asset Links
What if domain verification fails?	Rendering is unaffected; only verified App Links stop working	The app falls back to a Custom Tab with a visible browser toolbar
Google sign-in via WeWeb Auth	Blocked inside the WebView; needs a Custom Tab hand-off or native sign-in	Works, because the browser runs the flow
Notifications	Native push through OneSignal, Firebase or Pushwoosh	Web push through the browser; WeWeb's legacy plugin can't notify while the app is closed
Offline	Native fallback screen with reconnect	Whatever your custom service worker provides
Device features	Native modules such as scanners, biometrics, Play Billing and App Links	What the browser exposes to web pages

For WeWeb, the TWA's weak spot is the verification file. Digital Asset Links expects https://app.yourdomain.com/.well-known/assetlinks.json. In a 2023 community thread, a developer reported that WeWeb page paths can't contain dots, which rules out creating that file as a page, and the same question came up again in 2024. Open the URL in a browser before you commit to a TWA; if your JSON doesn't come back, users will see browser UI inside your app. The same file also powers verified App Links in a WebView app.

For most WeWeb apps – portals and internal tools with sign-in, uploads and notifications – a WebView app with native modules is the more predictable choice. A TWA suits a public, PWA-ready WeWeb app whose domain verification you fully control. Our PWABuilder comparison looks at TWAs in more depth.

Want your WeWeb app in Google Play without the trial and error?

Book a free consultation call: we check your web app, tell you which native features it needs and what to fix before review. Or hand it off – our App Specialists set up signing and CI/CD, prepare the store listing and submit the app for you.

Free consultation call Book our service →

Google Play groundwork before your first upload

Developer account. Register a Google Play Console account – personal, or organization if you represent a registered business (organizations need a D-U-N-S number). Google charges a one-time registration fee.
Verification. New personal accounts also complete device verification in the Play Console mobile app on a physical phone running Android 10 or higher.
Closed testing. Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for 14 consecutive days before they can apply for production access. Our 12 testers, 14 days guide explains how to pass it.
Format and signing. Google Play expects an Android App Bundle (AAB). With Play App Signing, Google holds the app signing key and you sign uploads with your upload key. Note both SHA-256 fingerprints: assetlinks.json needs the app signing one.
Target API level. Since August 31, 2026, new apps and updates must target Android 16 (API level 36) – see our target API level guide.
Policy basics. A public privacy policy URL, the content rating questionnaire, target audience, Data safety and sign-in details for reviewers, all under App content.

WeWeb features that need Android-specific handling

WeWeb feature	What happens on Android	How to handle it
Social sign-in through WeWeb Auth	Inside a WebView, Google answers with `disallowed_useragent` – a block in place since September 2021	Hand the flow to a Custom Tab or the browser and return through an App Link, add native Sign in with Google via Credential Manager (development work), or keep email and password for app users
Magic links (`/magic-link?token=…`)	The email link opens the browser, usually Chrome, so the session lands there instead of in your app	Verified App Links (`android:autoVerify="true"` plus `assetlinks.json`) or one-time codes typed in the app
File upload elements	In a WebView, nothing happens unless the app implements `onShowFileChooser`	Test every upload field on a device; offer a native document scanner for paper documents
Notifications from the legacy PWA plugin	Nothing arrives while the app is closed	Native push; on Android 13 and later, request `POST_NOTIFICATIONS` at a meaningful moment, not on first launch
Geolocation from the legacy PWA plugin	The WebView needs the app's location permission and a runtime prompt	Ask only where location is used and declare it in Data safety
Navigation in a single-page Vue app	The back button closes the app instead of going back; targeting API 36 turns predictive back on by default	Map back to WebView history via `OnBackPressedDispatcher`
Stripe checkout	Fine for physical goods and services; digital goods sold in the app fall under Google Play's payments rules	Google Play Billing for digital content; country-specific alternative billing programs exist

Targeting recent API levels also means your app draws edge to edge by default, so check that WeWeb headers and bottom navigation don't slide under the status bar or the gesture area. Test on a phone with gesture navigation and on one with three-button navigation.

The shortcut from WeWeb to Google Play

WebViewGold: your WeWeb app, native on Android

Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:

Push notificationsOneSignal or Firebase, for real, personal events
Native offline screenNo browser error pages when the connection drops
Native splash screenApp-like start instead of a loading web page
Deep linksLinks open the right screen inside the app
QR & barcode scannerDevice features the website alone can't offer
In-app purchasesNative purchase flows where the store requires them

No tool guarantees an approval: Google still judges what your app offers. Use the native features in your main user journey and keep proving that you own the website – our App Specialists review your WebViewGold app before it goes to Google Play.

Discover WebViewGold Let us submit your WebViewGold app

Building the WeWeb Android app with WebViewGold

WebViewGold – our team's own website-to-app product – includes a ready-made Android Studio project next to the iOS version. You enter the WeWeb URL, enable modules and build the bundle yourself or in the separately sold Cloud Builder.

Choose the package name carefully, for example com.yourcompany.portal. It can't change after the first release.
Point the app at your production subdomain (app.yourcompany.com), not <id>-production.weweb.io and never the staging address.
Set a custom user agent so WeWeb can hide web-only elements in the app – footer, the PWA install prompt – while features stay the same. If your pages set non-essential cookies, keep consent working in the app (natively if you hide the web banner).
Enable the modules your app needs: push via OneSignal, Firebase or Pushwoosh; the offline fallback with reconnect; App Links; biometric authentication; QR, barcode or document scanning; geolocation; the native Play review dialog; Google Play Billing with the Extended license.
Check the target API level in the project before you build: 36 for new apps and updates.
Build a signed AAB with your upload key, enroll in Play App Signing and add the app signing SHA-256 to assetlinks.json if you use App Links.
Upload to internal testing first and read the pre-launch report for crashes and for screenshots that show web error pages.

WebViewGold is a one-time purchase, you own the project and you publish it in your own Play Console account. Like any wrapper, it can't promise an approval – Google reviews what your WeWeb app does inside it.

Data safety and account deletion for a WeWeb backend

Google counts data collected through a WebView as your app's collection when your app controls that content – and with WeWeb, you control every page. Your Data safety answers therefore have to cover what your WeWeb workflows send off the device, not only what the native shell does:

Account data from WeWeb Auth, Supabase, Xano or Auth0, such as email address, name and user IDs.
Records users create in WeWeb tables or in your external database.
Order and payment details if Stripe handles physical purchases.
Location from geolocation actions, files from uploads and any analytics tags you added.
Content your workflows pass to OpenAI or another AI provider.

Account deletion has two halves on Google Play. Inside the app, add a clearly labeled delete option – in WeWeb, a settings page whose workflow calls your backend to remove the user and their data. Outside the app, publish a web page where people can request deletion without reinstalling, and enter its URL in the Data deletion questions. Don't restrict that page to WeWeb's authenticated users unless people can sign in there with the same method they use in the app; a plain request form works too. Our guides to the account deletion requirement and the Data safety section cover the edge cases.

Closed testing, review and release

For a new personal account, recruit closed testers from the people who will really use the app: colleagues for an internal tool, pilot clients for a portal. Keep 15 or more opted in, so a single dropout doesn't push you below 12. During the test, most fixes will happen in WeWeb and go live with a publish. That's useful, but Google tells developers to act on feedback during the test, so also ship a couple of new AABs with higher version codes and describe both kinds of changes in your production access answers. Google says the production access review usually takes seven days or less.

Before the production release, guard against Google Play's Webviews and Affiliate Spam rule, which targets apps that show a website without its owner's permission. Publish under the business that owns the WeWeb app's domain, use a contact email on that domain and link the Play listing from your site. The WebView spam guide lists the evidence reviewers can check. Then roll out in stages and watch the first crash reports.

appsubmitter.io handles the Play Console side end to end: account and app setup, upload key and Play App Signing, a CI/CD pipeline that builds and uploads AABs, the store listing, Data safety and content rating, closed-test planning and communication with the Google Play review team – all in your own developer account. Changes to your code or WeWeb project are quoted separately upfront. Book the Android service or schedule a free call first. If the iOS version was flagged for hidden features, read WeWeb app rejected under Guideline 5.6.

Checklist before you submit

The app loads your production custom subdomain, not a weweb.io, weweb-preview.io or staging address.
You chose between WebView and TWA – and for a TWA or App Links, /.well-known/assetlinks.json returns your JSON.
Google sign-in runs in a Custom Tab or the browser, or app users sign in with email and password.
Magic links open the app through verified App Links, or the app uses one-time codes instead.
Every WeWeb upload field works on a real device, and the back button walks through page history.
Notification permission is requested on Android 13 and later at a meaningful moment.
The AAB targets API level 36 and is signed with your upload key under Play App Signing.
Data safety covers what your WeWeb pages, Stripe, analytics and AI workflows collect.
Account deletion works in the app and through a public web page entered in Play Console.
Reviewer sign-in details are valid, need no one-time codes and unlock every role.
With a new personal account, at least 12 testers (better 15 or more) stay opted in for 14 days.

Frequently asked questions

Can I publish a WeWeb app on Google Play?

Yes. Package the published WeWeb app as an Android App Bundle – as a WebView app such as WebViewGold or as a Trusted Web Activity – and release it from your own Play Console account. It has to target API level 36, comply with Google Play's policies and come with complete Data safety and account deletion answers.

Do I need Android Studio to convert WeWeb to an Android app?

Not necessarily. WebViewGold ships an Android Studio project that you can open and build yourself, but the separately sold Cloud Builder configures and builds the app in your browser. If you'd rather not touch either, our team can set it up, and appsubmitter.io can build and upload the AABs through a CI/CD pipeline.

Can I use a TWA instead of a WebView for my WeWeb app?

Yes, if your WeWeb app qualifies as an installable PWA and your domain serves a valid /.well-known/assetlinks.json. Without that verification, the TWA shows a browser toolbar. A TWA handles Google sign-in well because the browser runs it, but its device features are limited to what the browser exposes to web pages.

Why does Google sign-in fail in my WeWeb Android app?

Since September 30, 2021, Google has blocked its OAuth sign-in in embedded WebViews and returns disallowed_useragent. WeWeb Auth's social sign-in opens a provider window, which in a WebView app runs inside that blocked context. Hand the flow to a Custom Tab or the browser and return through an App Link, or offer email and password. Changing the user agent is no fix: Google's policy forbids embedded user-agents under your control.

How long does Google Play review take?

Google doesn't publish a fixed review time for releases. For the separate production access application after closed testing, it says review usually takes seven days or less but can take longer. Plan buffer time for both, keep your reviewer sign-in details valid and close policy gaps first, because every rejection adds another round.

Do I really need 12 testers for my WeWeb app?

Only if you publish from a personal developer account created after November 13, 2023. Then you need a closed test with at least 12 testers opted in for 14 consecutive days before you can apply for production access. Organization accounts, which require a D-U-N-S number, aren't covered by that requirement.

Sources and further reading

Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.

Convert WeWeb to an Android App: WebView or TWA, Play Console Setup and Release