Convert Bolt to Android App: From bolt.new to Google Play

Key takeaways

Bolt has no Google Play button: wrap the published bolt.new site in an Android project, build an Expo project with eas build --platform android, or package a PWA as a TWA.
Google Play needs an Android App Bundle, Play App Signing and – since August 31, 2026 – target API 36; new personal accounts must also pass a 14-day closed test with at least 12 testers.
Bolt specifics: Google SSO must leave the WebView (Custom Tabs or Credential Manager), Supabase redirects need your app's links on the allow list, and Stripe only covers physical goods.
WebViewGold, made by our team, gives a wrapped Bolt site Play Billing, push, offline handling and App Links; appsubmitter.io handles Play Console, Data safety and the review.

Our recommended solution

Turn your Bolt app into a real Android app with WebViewGold

WebViewGold wraps the Bolt 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 ↓

How to convert Bolt to an Android app

To convert Bolt to an Android app, pick one of three routes: wrap your published bolt.new site in an Android Studio project such as WebViewGold, build an Expo project from Bolt with eas build --platform android, or add PWA features to the site and package it as a Trusted Web Activity. Each route ends with an Android App Bundle (AAB) that you upload to your own Google Play Console account – Bolt itself doesn't publish to Google Play.

The right route depends on what you already have. A Bolt web project – JavaScript frontend, Node.js backend, Bolt Database or Supabase, hosted on bolt.host, a custom domain or Netlify – is quickest to wrap. An Expo project only exists if you asked for a mobile app in your first prompt, because Bolt's docs say web projects don't switch over to mobile easily. Bolt's Expo guide walks through Play Console's internal testing and production release and notes that EAS hands you an APK or an AAB; for a new app on Google Play, it has to be the AAB.

A realistic timeline from bolt.new to Google Play

Phase	What happens	Bolt-specific watch-outs
1. Play Console account	Registration with a one-time fee as a personal or organization account (D-U-N-S for organizations); new personal accounts verify a physical Android phone	Register under the business name that matches your site's legal notice and domain
2. Packaging	Wrapper, Expo or TWA; a signed AAB with Play App Signing	Publish the site publicly first and point the app at the production domain, never a preview
3. Internal testing	Quick installs for your team and a pre-launch report	Look for web error pages and sign-in redirects that end on localhost
4. Closed test	Personal accounts created after November 13, 2023: at least 12 testers opted in for 14 consecutive days	Every Update reaches testers instantly – still ship a few native builds so Play Console shows progress
5. Production access	An application with specific answers about the test; Google says this review usually takes seven days or less	Log what testers reported and what you changed in Bolt
6. Production release	Policy review, then a staged rollout	Keep reviewer sign-in details valid and the Data safety form current

Organization accounts aren't subject to the closed-test rule, but they must represent a real registered business – our closed testing guide covers both cases and how to recruit testers legitimately.

Want your Bolt 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 →

Route A: your published Bolt site in a WebViewGold Android project

WebViewGold is the website-to-app solution made by our team: an Android Studio project you point at your production URL and configure in one file, bought once and published in your own account. Without a local Android Studio setup, the Cloud Builder builds it in the browser. For a Bolt site on Android, these settings do the heavy lifting:

URL handling. Keep your own domain inside the app, send Google's sign-in page to Chrome Custom Tabs – Google blocks OAuth inside WebViews – and open external sites and physical-goods checkouts in the browser.
Supabase redirects. Add your App Links domain or custom scheme to the URI allow list in Bolt, so sign-in and confirmation redirects can return to the app, and test the round trip on a device.
Uploads. Bolt Cloud's file storage only helps if upload fields work in the app; the document scanner adds a Scan document option to the upload dialog.
Push. OneSignal, Firebase or Pushwoosh, triggered from a Bolt server function when something happens for the user, with the POST_NOTIFICATIONS prompt on Android 13+ shown at a sensible moment.
Navigation and back. A Material drawer or bottom bar for your main sections; check that the predictive back gesture, on by default when you target API 36, walks back through your pages.
Offline. A fallback page with a reconnect button instead of Chrome's error screen.
Payments. Google Play Billing for credits, plans or premium features (Extended license), with purchase history available to your web app.
App Links. Shared URLs open in the app once assetlinks.json on your domain lists your package and the Play App Signing fingerprint – make sure your hosting serves that path.

Route B: an Expo build from Bolt for Google Play

Create the project in Bolt with mobile app in the first prompt and test it with Expo Go via the Device Preview QR code.
Download the code, install the EAS CLI and run eas init and eas build:configure.
Run eas build --platform android with a build profile that outputs an AAB. EAS can generate and manage the Android keystore; Play App Signing then holds the app signing key on Google's side.
Check the target API. Expo SDK 54 and newer ships React Native 0.81, which targets API 36; older projects can set it through expo-build-properties before a new build.
Upload the AAB to internal testing, then to the closed testing track.

Native features come from Expo modules – notifications via Firebase Cloud Messaging, camera, biometrics – and Bolt's docs link RevenueCat's guide to adding Play Billing subscriptions to a Bolt-generated Expo app. For Google sign-in, use a native flow built on Android's Credential Manager rather than a web view. Every change to the app means a new build and a new release in Play Console.

The shortcut from Bolt to Google Play

WebViewGold: your Bolt 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

Route C: a Trusted Web Activity – only if your Bolt site is a real PWA

A TWA shows your site full screen in the user's Chrome rather than in a WebView, so Google sign-in behaves exactly as on the web, and Play Billing is possible through the Digital Goods API. The catch for Bolt: its docs say nothing about PWAs, so you prompt Bolt for a web app manifest and a service worker with an offline page yourself. PWABuilder, Microsoft's open-source packager, then builds the AAB with Bubblewrap and can generate the signing key.

The app only runs without a browser bar if /.well-known/assetlinks.json on your domain confirms that app and site belong together – with the SHA-256 fingerprint of the Play App Signing key, not just your upload key. Without native modules, the value has to come from the PWA itself; otherwise Google's limited functionality rule bites a TWA just as it bites a thin wrapper.

Google Play requirements for Bolt apps at a glance

Requirement	What Google expects	What it means for a Bolt app
Target API level	API 36 for new apps and updates since August 31, 2026	Check the built AAB on every route – see the target API guide
Webviews and Affiliate Spam	No apps that mainly show a website without its owner's permission	Publish as the business that owns the domain, with matching developer name, email and website – details in the WebView spam guide
Limited functionality	No static apps without app-specific features	Native navigation, push, offline handling and billing instead of a bare bolt.host frame
Data safety	Everything the app, its SDKs and web content you control collect	Supabase account data, Stripe, analytics, push tokens, uploaded files
Account deletion	In the app and through a public web page linked in Data safety	Bolt's User Management only lets you delete users yourself – build a user-facing flow and a request page, as the deletion guide explains
Payments	Google Play Billing for digital goods, with country-specific alternative billing exceptions	Bolt's Stripe integration for physical goods and services only
Consistent behavior	The same app for reviewers and users under the Deceptive Behavior policy	No feature Updates that change the reviewed app – the release discipline from Bolt and Guideline 5.6 applies here too

Publishing the Bolt app with appsubmitter.io

appsubmitter.io takes the Play Console side off your hands: account and app setup, upload key and Play App Signing, a CI/CD pipeline for the AAB – fastlane with GitHub Actions or Codemagic on the repository Bolt syncs to – the store listing, Data safety, a plan for the closed test, your production access answers and every exchange with Google's review team. The app stays in your own developer account. Code changes, such as a delete-account flow, are quoted separately upfront.

Book the Android service or work out the right route for your Bolt project in a free consultation call. For iPhone, our guide to converting Bolt to iOS weighs the same two main routes against Apple's rules.

Checklist before you submit

You picked a route – WebViewGold wrapper, Expo build or TWA – and you upload an AAB, not an APK.
The bolt.new site is published publicly on your production domain, without the Made in Bolt badge.
The bundle targets API level 36, and Play App Signing is active.
Google sign-in runs in Custom Tabs or a native Credential Manager flow, never inside the WebView.
Site URL and URI allow list include your production domain and the links your app uses.
The notification permission is requested at a meaningful moment on Android 13 and later.
assetlinks.json lists your package and the Play App Signing fingerprint (App Links or TWA).
Data safety covers Supabase, Stripe, analytics, push and uploaded files.
Users can delete their account in the app and request deletion on a public web page.
For a new personal account, at least 12 testers stay opted in for 14 consecutive days.

Frequently asked questions

Can I put a bolt.new app on the Google Play Store?

Yes. Package the published bolt.new site with a wrapper such as WebViewGold or as a Trusted Web Activity, or build an Expo project from Bolt with EAS. You upload the AAB in your own Play Console account, and new personal accounts first run a closed test with at least 12 testers for 14 consecutive days before production.

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

Not necessarily. EAS builds Expo projects in Expo's cloud, PWABuilder packages a TWA online, and WebViewGold's Cloud Builder builds a wrapper app in the browser. Android Studio comes in when you build the WebViewGold project yourself or want to debug the app on a device or emulator before uploading it.

APK or AAB: which file does Google Play need?

An AAB. Google Play has required the Android App Bundle for new apps since August 2021, and it works together with Play App Signing, where Google holds the app signing key. Bolt's Expo guide mentions that EAS can produce an APK or an AAB – APKs are handy for quick device tests, but Play Console uploads should be bundles.

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

Yes, if you turn the Bolt site into a proper PWA first – Bolt doesn't document one, so you add the manifest and service worker yourself. A TWA runs in the user's browser, so Google sign-in works as on the web, and Play Billing is possible through the Digital Goods API. You need a valid assetlinks.json on your domain and get fewer native features than with a wrapper.

How long does it take to get a Bolt app live on Google Play?

For a new personal account, the closed test alone takes 14 days, and Google says the production access review usually takes seven days or less. Certain apps also get extended reviews of up to seven days, or longer in exceptional cases. Packaging is the short part – plan the test and the policy forms early.

WebViewGold or Expo: which is better for a Bolt app on Android?

WebViewGold, which our team builds, is the faster route if your Bolt web app already works: one codebase, web updates through Update, native modules for billing, push, offline handling and App Links. Expo suits apps that are mobile-first, at the price of a new project and a rebuild for every change. Neither can promise an approval.

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 Bolt to an Android App: Wrapper, Expo or TWA – and the Steps to Google Play