Short answer
Bolt.new apps reach Google Play in one of two ways: a deployed web project wrapped as an Android app with WebViewGold (or a Trusted Web Activity), or an Expo project compiled into an Android App Bundle. Android builds do not need a Mac, so this is often the faster store to start with; the usual blockers are environment variables, back navigation, uploads and Play's testing rules.
On this page
Android is often the easier first store
For Bolt.new users without a Mac, Google Play is a natural starting point. Android builds run on Linux, Windows or macOS, cloud build services handle them well, and Google is generally more tolerant of web-based apps than Apple, provided they add value. Starting on Android also gives you real user feedback before you tackle App Review.
Bolt.new can produce two kinds of projects, and they take different roads.
- Web projects (Vite with React, Next.js, Astro and others) are deployed to a host such as Netlify, then packaged as an Android app.
- Expo projects are React Native apps and compile to a native Android App Bundle.
Check package.json: expo and react-native mean the Expo road; otherwise it is the web road.
The web road
Deploy properly
The in-browser preview in Bolt is a development environment, not a server. Deploy to a production host, attach a custom domain and set all environment variables there. The Bolt production guide lists what usually breaks during that move.
Package it
Two choices:
Native wrapper. WebViewGold comes as an Android Studio template. Set your URL, package name, icon, splash and colours, switch on native features (push notifications, offline handling, file downloads, native share) and build a signed App Bundle. You pay once and keep the full project. If you would rather not open Android Studio, WeSetupYourWebViewApp delivers the configured app with full source code in about 72 hours.
Trusted Web Activity. If the app is a solid PWA, a TWA renders it in the user's browser engine without browser UI. You publish /.well-known/assetlinks.json on your domain with the package name and the Play App Signing certificate fingerprint. On a static host, place the file in the build output (for Vite, the public folder) and confirm it is served as JSON, not swallowed by a single-page app redirect rule.
Choose the wrapper when you need native push, file handling or control over login flows; choose a TWA for simple, public, content-style apps.
The Expo road
- Leave the browser. Push the Bolt project to GitHub or download it, install dependencies locally, and run it on an Android device or emulator to confirm it works outside Bolt.
- Configure Android in the app config. Set
android.package,versionCode, adaptive icon, splash and the permissions you actually need. Remove permissions you do not use; Play asks about sensitive ones. - Build an App Bundle. Expo's build service (EAS Build) produces a signed
.aabin the cloud, or you generate the native Android project and build with Gradle yourself. Either way, keep the upload keystore safe, ideally managed by the build service or your secrets store, and enrol in Play App Signing. - Test a release build. Development builds hide problems: missing environment variables, Hermes-specific errors, or native modules not linked. Install the release build on a real device before uploading.
For continued React Native development after launch, apprat.io builds and maintains Android and iOS apps with AI-assisted development plus human developer hours.
Common Bolt-to-Android failures and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| White screen on launch | VITE_ or EXPO_PUBLIC_ variables missing in production | Set them on the host or in the build profile |
| 404 after navigating and reopening | SPA redirect rule missing on host | Add a rewrite of unknown paths to index.html |
| Back gesture closes the app | Router does not use browser history in the wrapper | Use history-based routing and test back on every screen |
| File upload button does nothing | WebView file chooser not handled | Use a wrapper that supports file chooser and camera capture |
| Google sign-in error | OAuth blocked in embedded web views | Open sign-in in a Custom Tab and deep link back |
| API calls fail only in the app | Hard-coded preview URLs or CORS rules | Point to production APIs and allow your domain |
| Crash on start (Expo) | Native module or config mismatch in release build | Rebuild after expo prebuild checks and read the device logs |
Play Console requirements, applied to Bolt apps
Testing before production. New personal developer accounts must run a closed test (currently 12 testers opted in for 14 continuous days) before production access. Organization accounts are exempt. Either way, start with internal testing; see TestFlight and Play Console internal testing.
Data safety. Bolt projects often use Supabase or another backend for auth and data, plus third-party APIs. List what you collect and which services receive it.
Account deletion. If users can register, provide deletion in the app and a public web link that you enter in the Play Console.
Target API level. Google requires apps to target a recent Android API level and raises the bar yearly. Expo SDK upgrades and WebViewGold updates are how you keep up; schedule them.
Secrets. Bolt makes it tempting to call paid APIs directly from client code. Anything in the app bundle can be extracted. Move secret calls to server functions.
Value beyond the website
Play's minimum functionality policy is less strict in practice than Apple's 4.2, but a pure website wrapper still risks rejection and poor ratings. Add notifications for real events, camera or file features, sensible offline behaviour and an Android-native back experience. Our list of Google Play rejection reasons for converted web apps shows which issues come up most.
Release
Upload the bundle, test in internal and closed tracks, complete listing, content rating and Data safety, then roll out in stages. appsubmitter.io does submissions, listings, CI/CD and rejection handling in your own Play Console if you prefer to hand that off.
FAQ
Can I publish a Bolt.new app to Google Play without Android Studio?
For Expo projects, a cloud build service can produce the App Bundle. For web projects, you need a wrapper project built in Android Studio, a TWA generator, or a service that builds it for you.
APK or AAB for Google Play?
New apps on Google Play are published as Android App Bundles (.aab). APKs remain useful for direct testing on devices.
Is a Trusted Web Activity enough for a Bolt app?
For public, PWA-quality apps, often yes. For apps with login, uploads and push notifications, a native wrapper gives you more control and fewer surprises.
Should I start with Google Play or the App Store?
Without a Mac, Google Play is usually faster. Many teams launch on Android, learn from real users, then prepare the iOS version.