BUBBLE → PLAY STORE
Publish your Bubble app to the Google Play Store
Updated November 10, 2026
The one thing Bubble doesn't give you
Bubble deploys your app to a live URL and handles hosting, the database and your workflows beautifully. What it doesn't produce is a signed Android App Bundle — the only thing Google Play accepts. Building that by hand means the Android SDK and a keystore you must generate and never lose. SaasToStore closes that gap from your existing URL, with a Capacitor native build that needs no manifest and no service worker.
From Bubble to the Play Store, step by step
- 01 ·
Deploy your Bubble app to live
In the Bubble editor, push your app from Development to Live. Your public address is yourapp.bubbleapps.io, or your custom domain on a paid plan.
- 02 ·
Paste it into SaasToStore
We fetch your icon and app metadata. You choose the build: we recommend the Capacitor build, which needs no service worker and no config from you.
- 03 ·
We build & sign the .aab
A signed Android App Bundle with a unique RSA-2048 keystore, encrypted and kept for your future updates.
- 04 ·
Get the files for the stores
A paid build delivers the signed files each store asks for: the .aab for Google Play. Each store sets its own review time.
Bubble to APK: the files you get
A paid Android build of your Bubble app gives you two files of the same signed app. The .apk installs straight on an Android phone, yours or a tester's, without going through a store. The .aab is the format Google Play asks for. Both are signed with your app's key, and that same key is reused for every update, so each new version installs over the previous one.
Android Build (Native) — the build for Bubble
- Any Bubble URL, with or without a service worker
- A signed .aab and .apk under your app's name and icon
- The same signed app goes to Google Play, the Amazon Appstore and the Samsung Galaxy Store
- Takes native tabs and menus, and plugins such as push notifications
Free test build
- An .apk with the SaasToStore logo, for your own phone
- Shows your Bubble app as an app before you pay
- Shows an address bar at the top of the screen
- Not a file to publish: no .aab, no store
What works inside your Bubble Android app
- Every page and every navigation of your live Bubble app
- Your responsive settings: the app shows Bubble's layout at the phone's width
- Email and password sign-in, as on your site
- File and picture uploaders: the phone's own picker takes a photo or picks a file, with no permission to set up
- Changes you push to live, from text to workflows, with no new build
Two things behave differently from the browser. Google refuses sign-in inside an embedded web view, so Google sign-in needs one setting; sites that keep the session in server cookies hide the Google button in the app and keep email sign-in there. The sign-in guide covers both cases. And only your domain and its subdomains stay inside the app: a link to another domain, such as an external payment page, opens in the phone's browser, unless you add that domain to Extra domains in your project before the build.
A new build is only needed when the native part of the app changes: its icon, name or launch screen, its tabs and menus, a plugin, or the address of your site.
Doing it yourself vs with SaasToStore
A typical Bubble launch
A maker ships a two-sided marketplace in Bubble — listings, accounts, Stripe payments via the API connector. Their users keep asking for "an app." Instead of rebuilding natively, they deploy to live, paste their bubbleapps.io URL into SaasToStore, and get a signed bundle in minutes. Because the app loads the live URL, every workflow they ship afterwards appears in the installed app instantly — no resubmission for everyday changes. Same source, now on Google Play and on desktop.
What you get for your Bubble app
- Signed Android App Bundle (.aab) + APK for Google Play
- Capacitor build — works even though Bubble has no service worker
- Your workflows, database, plugins and API calls keep running live
- Encrypted keystore kept for seamless updates
- Optional AI-generated Play Store icon, screenshots and description
- Same URL also builds Windows, macOS and Linux desktop apps
- Signed .ipa for the App Store from the same URL — iOS included in SHIP
- One-time pricing: €39 for every platform — no monthly lock-in
On another tool too? See Lovable, Webflow, Framer and any website → APK.
Frequently asked questions
Where do I get the URL to paste from Bubble?+
Deploy your app to live in the Bubble editor, then use your yourapp.bubbleapps.io address — or your custom domain if you're on a paid Bubble plan (custom domains require a paid plan). Paste that public HTTPS URL into SaasToStore.
Does a Bubble app need a service worker or manifest?+
Bubble apps usually don't ship a service worker, and you don't need one. You choose the build: the Capacitor build, which we recommend for Bubble, wraps your app in a full native Android shell with no manifest and no service worker. The TWA build reads your web manifest and hides the address bar once an assetlinks.json file is on your domain; a service worker only helps offline.
Will my Bubble workflows, database and plugins keep working?+
Yes. The app loads your live Bubble deployment, so your workflows, data, API connector calls and plugins run exactly as they do in the browser. Nothing in your Bubble app changes.
Is the result a real native app or a webview?+
It installs and runs like a native app — its own icon, full screen, no browser bar. Bubble's responsive engine renders normally inside the shell.
Do I need Android Studio or any coding?+
No. SaasToStore builds and signs the Android App Bundle in the cloud. You only need a Google Play Console account to upload the signed .aab we deliver.
How fast can a Bubble app be on the Play Store?+
The build takes a few minutes. After that, the review time is set by Google Play, not by us.
Can I update my Bubble app after publishing?+
Yes. Because the app loads your live Bubble URL, most content and logic changes appear instantly with no rebuild. You only rebuild for a new icon, name or native capability — and we reuse your keystore so updates stay accepted.
Can my Bubble app also run on desktop?+
Yes. The same Bubble URL also produces Windows (.msi), macOS (.dmg) and Linux (.AppImage) installers — your Bubble app as a desktop program, no extra work.
Can I publish my Bubble app to the App Store as well as Google Play?+
Yes. The same Bubble URL also produces a signed .ipa for the App Store — iOS is included in SHIP together with Android and desktop, so you are not buying a second product. You submit it under your own Apple Developer account (99 USD/year); we build and sign, you own the listing.
Will Apple approve a Bubble app published this way?+
Apple reviews wrapped web apps more strictly than Google does. App Store Review Guideline 4.2 asks for an app that does more than reopen a website, so your Bubble app needs real app value — an account, saved state, notifications, something a bookmark cannot do. Apps that are genuine products pass; a marketing page wrapped in a shell does not. Google Play applies a comparable rule but enforces it more loosely, which is why an app can clear Play and still be rejected by Apple.
Ready to ship?
Paste your URL. We handle the build. You publish to the store.
Publish now