Key takeaways
- Bubble's native builder emails you an AAB on the first Android deploy; a WebView wrapper gives you an Android Studio project you build and sign yourself.
- Guard the keystore and its passwords: Bubble's own documentation warns that you can't push updates without it.
- New personal Play Console accounts need 12 testers opted in for 14 days before production access – start the closed test as soon as a stable build exists.
- Google expects proof that the WebView shows your own site, an honest Data safety form, account deletion in the app and on the web, and Play Billing for digital goods.
Our recommended solution
Turn your Bubble app into a real Android app with WebViewGold
WebViewGold wraps the Bubble 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.
Can you convert a Bubble app to an Android app?
Yes. You can convert Bubble to an Android app in two ways: Bubble's native mobile builder generates an Android App Bundle (AAB) from the mobile views you design in the editor, or a WebView wrapper such as WebViewGold turns your live Bubble web app into an Android Studio project. Both end the same way – with an AAB in Google Play Console, published from your own developer account.
The gatekeeping is what differs from the App Store. Google judges thin wrappers through its own policies – Webviews and Affiliate Spam, plus Limited Functionality and Content – and adds requirements Apple doesn't have: a testing period for new personal accounts, a target API level that rises every year and declarations that must match the app's behavior. This guide covers those Google Play specifics; the App Store side is in our Bubble to iOS guide.
Native builder, WebView wrapper or TWA: which package fits your Bubble app?
| Route | What you upload | Signing | Watch out for |
|---|---|---|---|
| Bubble native mobile builder (public beta) | An AAB Bubble generates; the first one arrives by email, later deploys can upload automatically | A keystore Bubble generates or you supply – lose it and you can't update | Mobile views to build; in-app purchases are subscriptions only; Bubble publishes to the Play Store only, no other Android stores |
| WebView wrapper (WebViewGold for Android) | An AAB you build from the Android Studio project or with Cloud Builder | Your upload key plus Play App Signing | Native features have to carry the core journey |
| Trusted Web Activity (Bubblewrap or PWABuilder) | An AAB that opens your site full screen in the user's browser | Your key; Digital Asset Links verify site and app | Needs a web app manifest and /.well-known/assetlinks.json on your domain |
Two Bubble facts narrow the choice. Bubble can't export your app as code, so there is no "bundle the web build into the app" option – every route except the native builder loads the live Bubble app from your domain. And Bubble's manual has no pages on PWA setup or on serving files under /.well-known/, which a TWA and verified App Links both rely on. Confirm you can publish those files before you plan around them.
Want your Bubble 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.
Google Play groundwork: account, testers, target API and keys
- Developer account. Register a Google Play Console account as a person or an organization; registration is a one-time fee. Organizations need a D-U-N-S Number, and new personal accounts verify a physical Android phone in the Play Console mobile app.
- Testing requirement. On personal accounts created after November 13, 2023, the production access application only unlocks after a closed test in which at least 12 testers stayed opted in for 14 consecutive days; internal testing doesn't count. Bubble's Play Store guide tells you to upload the first AAB under Production – on such an account, use a closed testing track instead. Our closed testing guide explains how to pass the application.
- Target API level. Since August 31, 2026, new apps and updates must target Android 16 (API level 36), with extensions to November 1, 2026 on request. In a wrapper you set
targetSdkyourself. With Bubble's builder you don't touch the Gradle files, so check the target shown for each bundle in App bundle explorer – the target API guide covers the rules. - Keys. New apps published as app bundles use Play App Signing: Google holds the app signing key, and the key you sign uploads with acts as your upload key. Bubble generates a keystore for you and warns that if it is lost, you won't be able to push updates – store the file, alias and passwords in a password manager on day one. For automatic uploads, Bubble also needs a Google Cloud service account JSON key with access to your Play Console and the Google Play Android Developer API enabled.
Make a wrapped Bubble app behave like an Android app
Back gesture and predictive back
Android users expect the back gesture to move one page back inside the app and to leave it only from the start screen. Apps that target API 36 get predictive back by default, and onBackPressed() is no longer called, so the wrapper has to handle back navigation through the newer callbacks. Test it on gesture and three-button navigation.
File and picture uploads
Bubble's File Uploader and Picture Uploader ask the browser for a file picker. An Android WebView shows nothing unless the app implements onShowFileChooser – the classic dead upload button of thin wrappers. WebViewGold's Android project brings the upload dialog along, and its document scanner adds a "Scan document" option to it.
Notification permission
Android 13 and later require the POST_NOTIFICATIONS runtime permission before any push appears. Ask when the value is obvious – after a first booking, not on first launch. Push runs on Firebase Cloud Messaging under the hood: Bubble's native builder takes the Firebase files in its mobile settings, and WebViewGold supports OneSignal, Firebase or Pushwoosh.
Google sign-in
Bubble's Google login plugin runs a web OAuth flow, and Google blocks such flows in embedded WebViews with a disallowed_useragent error. On Android, Google points developers to Custom Tabs; a native sign-in through Credential Manager works too. If neither fits version 1, offer email and password in the app and keep Google login on the website. In Bubble's native builder, Sign in with Apple on Android already runs through the system browser.
Links and lost connections
Keep your own domain inside the app and open every other domain in a Custom Tab. Replace the WebView's default error page with a native offline screen – WebViewGold's Reconnect API reloads the last page once the connection is back.
The shortcut from Bubble to Google Play
WebViewGold: your Bubble 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.
The Google Play policies your Bubble app has to clear
| Policy | What Google looks for | What it means for a Bubble app |
|---|---|---|
| Webviews and Affiliate Spam | A webview of a site shown without the owner's permission | Publish under the business that owns the Bubble app and its domain, with matching developer name, contact email and website – see the WebView spam guide |
| Limited Functionality and Content | Apps that are "static without app-specific functionalities" | Native navigation, push, scanning or offline value in the main journey |
| Data safety | Everything the app, its SDKs and WebView content you control collect | Bubble user data, uploaded files, analytics plugins, push tokens and payment data – see the Data safety guide |
| Account deletion | A deletion path inside the app plus a web resource whose URL you enter in Play Console | Bubble builds web pages anyway: add a "Delete account" workflow to the app and a public request page – see the account deletion guide |
| Payments | Google Play Billing for digital goods and services | Native builder: Play Billing subscriptions; wrapper: WebViewGold's Play Billing module (Extended license); physical goods keep Stripe. Country-specific alternative billing programs exist |
| Deceptive Behavior | Hidden or dormant features and apps that behave differently for reviewers | The same discipline as for Apple: no conditions that hide features from the review login – see Bubble and Guideline 5.6 |
A release plan from the first AAB to production
- Create the app in Play Console and complete App access with a reviewer login – Bubble's own FAQ names apps that require login without a test account as a common problem – plus content rating, target audience, privacy policy and Data safety.
- Get the first AAB. With the native builder, the first deploy fails on purpose and Bubble emails you a link to the bundle; with a wrapper, build it in Android Studio or Cloud Builder.
- Upload to internal testing and read the pre-launch report: crashes, blank screens and dead buttons show up there first.
- Run the closed test on a personal account. Recruit more real testers than the minimum, because anyone who opts out has to start their 14 days again, and ship at least one update based on their feedback. Fixes you deploy in Bubble go live without a new bundle – log them anyway, because the production access questions ask what you changed.
- Apply for production access with specific answers. Google says the decision usually takes seven days or less, sometimes longer.
- Release with a staged rollout and watch Android vitals and reviews.
- Keep updates clean: every native change needs a higher
versionCode, the same upload key and a bundle that meets the current target API level.
Google also says certain apps and developer accounts get extended reviews of up to seven days, or longer in exceptional cases. For a new app, the closed test and the reviews decide your launch date more than the build does.
WebViewGold, appsubmitter.io and the alternatives
WebViewGold for Android, made by our team, is a ready-made Android Studio project: you enter your live Bubble URL, switch on modules and build the AAB yourself or with the separately sold Cloud Builder. For Bubble apps on Google Play, the useful modules are Google Play Billing, push via OneSignal, Firebase or Pushwoosh, the Material navigation drawer and bottom bar, biometric login, QR, barcode and document scanning, App Links, the offline page with Reconnect, Custom CSS & JS injection, a custom user agent and the native Play review dialog. It is a one-time purchase, and the project and the listing stay yours.
WebViewGold isn't the only wrapper Bubble makers use – our look at Natively alternatives covers subscription-based services too. And if your app needs native screens more than web parity, Bubble's own builder is the honest choice.
appsubmitter.io handles the Google Play side in your own developer account: upload key and Play App Signing, a CI/CD pipeline for release bundles, the store listing and Data safety form, a plan for the closed test and your production access answers, the submission and the communication with Google's review team. Code changes aren't included; we quote them upfront. Book the Android service or start with a free consultation call.
Checklist before you submit
- You picked a route: Bubble's native builder, a WebViewGold wrapper or a TWA whose files you can actually host.
- The Play Console account is verified, and a personal account has a closed test with 12+ opted-in testers planned for 14 days.
- Every bundle targets API level 36, checked in App bundle explorer.
- The keystore, alias and passwords are backed up outside Bubble.
- Back navigation, file uploads and the notification permission work on a real Android phone.
- Google login never runs inside a WebView – it uses a Custom Tab or Credential Manager, or stays on the website.
- Developer name, contact email and website match the business that owns the Bubble app and its domain.
- The Data safety form covers user data, uploads, analytics plugins and push tokens.
- Users can delete their account in the app and request deletion on a public web page.
- Digital goods use Google Play Billing; Stripe is limited to physical goods and services.
Frequently asked questions
How do I convert a Bubble app to an Android app without coding?
Do I need Android Studio to publish a Bubble app on Google Play?
How long does Google Play review take?
Can I use a Trusted Web Activity for my Bubble app?
/.well-known/assetlinks.json on your domain – Bubble's manual covers neither. A verified TWA proves that you own the site, but it adds no native features, so it can still fall short of Google's Limited Functionality and Content policy.What if I lose the keystore Bubble generated for my app?
Does Bubble's native builder support Google Play Billing?
Recommended solution
From Bubble to Google Play: WebViewGold + appsubmitter.io
- 1 Build with WebViewGold Turn your website into native iOS and Android projects.
- 2 Add native value Push, offline screen, deep links or scanning in your main flow.
- 3 We submit it Our App Specialists submit and talk to the review team.
WebViewGold is made by our team (jocapps GmbH). It is a tool, not a guarantee – approval decisions are made by Apple and Google.
Sources and further reading
- Bubble Manual – Publishing to the Google Play Store
- Bubble Manual – Native mobile publishing FAQ
- Bubble Manual – In-app purchases (StoreKit and Google Play Billing)
- Play Console Help – App testing requirements for new personal developer accounts
- Play Console Help – Target API level requirements for Google Play apps
- Google Play Policy Center – Spam (Webviews and Affiliate Spam)
- Google Developers Blog – OAuth changes for embedded webviews (June 29, 2021)
- WebViewGold for Android – documentation
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.