GOOGLE PLAY PUBLISHING
Publish Your App to Google Play — No Android Studio, No Code
SaasToStore handles the entire technical stack automatically. You provide a URL. We generate the Play Store assets (icon, feature graphic, screenshots) and the metadata package, and a paid build delivers the signed .aab Google Play asks for. The free build is a test APK with the SaasToStore logo: install it on your phone to see your app.
Updated November 10, 2026
Why put your SaaS or website on Google Play
A Google Play listing puts your product on your users' home screen, lets you bring them back with push notifications, and opens a discovery channel that doesn't depend on search or ads. Nothing has to be rewritten: the app opens the web app you already run, so your dashboard, customer portal, booking flow or store keeps a single codebase. Any HTTPS address works.
Everything Google Play requires — handled automatically
How to publish to Google Play in 4 steps
- 01 ·
Check your site (free, 10 seconds)
Paste your URL into our PWA Checker. It reads your web manifest, icon and service worker. A service worker is recommended for offline use, not required.
- 02 ·
Build your app
Create a project, configure your app name, package ID and target market, then launch the build.
- 03 ·
Get your signed files
A few minutes later, a paid build delivers the signed .aab Google Play asks for, an APK for your own phone, the store assets and a metadata package.
- 04 ·
Submit for review
Google Play sets the review time: a new app usually waits longer than an update. The builds request no unnecessary permissions.
PWA or not: two Android builds for Google Play
Google Play distributes Android apps, not web pages, so your site has to be wrapped in an Android shell. There are two ways to do it, and you pick the one that fits your site.
Android Build (Web) — TWA
- A Trusted Web Activity: your site opens full screen in Chrome's engine
- A very small app that updates with your site
- Reads your site's web manifest; a service worker is recommended for offline use, not required
- You host the assetlinks.json file we give you, which removes the address bar
Android Build (Native) — Capacitor
- Your site inside a native Android shell
- Works with any website, no service worker needed
- Adds native tabs and menus, and plugins such as push notifications, biometric unlock and in-app purchases
- The build we recommend for most sites
With a paid build, both give you a signed .aab for Google Play and an .apk to install on your own phone. The free test build is an .apk with the SaasToStore logo: it shows you the app on your phone, it isn't a file to publish.
Works with the builder you already use
Sites made with Bubble, Webflow, Softr or Glide work with the Native build, which accepts any site, service worker or not. The Web build reads the site's web manifest: it suits a site that already has one, such as a Lovable or Framer PWA.
Free test build or paid build
What's included with a paid build
- Signed Android App Bundle (.aab) with 2048-bit RSA keystore
- 512×512 icon + 1024×500 feature graphic, AI-generated
- Screenshots for phone and tablet
- Digital Asset Links (assetlinks.json) — generated for you to host on your domain
- Store listing: title, short description, full description (AI-generated)
- Privacy Policy URL — auto-generated and hosted
Go deeper
Frequently asked questions
Do I need a Google Play Developer account to use SaasToStore?+
To publish on Google Play, yes: Google charges a one-time $25 developer registration fee. You don't need the account to build your app or to test it on your phone. SaasToStore handles the app building and signing; you manage your Play Console account.
How long does Google Play review take?+
Google sets the review time, and it varies: a new app usually waits longer than an update. A paid SaasToStore build delivers the signed .aab Google Play asks for, targets API 36 and requests no unnecessary permissions.
Can SaasToStore publish directly to Google Play, or do I have to upload manually?+
A paid build delivers the signed .aab Google Play asks for, along with the store assets, ready to upload in your Play Console. The free build is an APK to test the app on your phone.
What happens when I need to update my app?+
Each update uses one build credit. SaasToStore reuses your existing keystore automatically — critical, as Google Play rejects updates signed with a different key. Your keystore is stored encrypted and tied to your project.
Can I publish a Bubble or Webflow site to Google Play?+
Yes. Our Native build (Capacitor) works with any site, service worker or not, which covers Bubble and Webflow projects. The Web build (TWA) is open to them too once the site serves a web manifest: you choose the build type.
Can I put a SaaS web app on Google Play?+
Yes. Your SaaS keeps running on the web: SaasToStore wraps it in an Android app, as a Trusted Web Activity or in a native shell, and a paid build produces the signed .aab Google Play accepts. No native rewrite, no Android Studio.
Do I need a new build every time I update my site?+
No. The app loads your live site, so new content and features reach your users as soon as you deploy them. You only need a new build when the app itself changes: its name, icon, permissions, plugins or native navigation.
My SaaS sells subscriptions. What does Google Play require?+
In most countries, digital goods and subscriptions sold inside the app must go through Google Play Billing. Customers who already pay on your website can sign in and use what they pay for, as long as the app doesn't send them to buy outside Google Play. To sell inside the app, Google Play subscriptions work through the RevenueCat module built into the Native build.
Ready to ship?
Paste your URL. We handle the build. You publish to the store.
Check my app — free