Deploy & App Stores

How to Publish a Bolt.new App on Google Play

For a Bolt.new Expo project, the fastest route to Google Play is EAS Build to produce a signed .aab and EAS Submit to upload it, after a first manual upload in Play Console. For a Bolt web app, wrap it with Capacitor and build in Android Studio. In both cases, new personal developer accounts must finish a 14-day closed test with 12 testers before going live.

neooutput editorial team 4 min read Auf Deutsch lesen

How do you build a Bolt Expo app for Android?

Use EAS Build with a production profile, which outputs an Android App Bundle by default. EAS can generate and store the upload keystore for you, which is convenient but means you should also download a backup.

Set the android.package in app.json once; it becomes your permanent Play Store identity.

  1. Export the Bolt project and run npm install
  2. Set android.package, version and android.versionCode in app.json
  3. Run eas build --platform android --profile production
  4. Download the .aab and the keystore backup from your Expo account
  5. Create the app in Play Console and upload the first .aab manually to internal testing

How does EAS Submit work with Google Play?

EAS Submit uploads Android builds through the Google Play Developer API using a Google Cloud service account key. You create the service account, grant it access in Play Console and give EAS the JSON key.

Google requires the first upload of a new app to happen manually through Play Console, which is why the first build goes in by hand. After that, eas submit --platform android can push builds to internal, closed or production tracks.

What about Bolt web apps on Android?

A Bolt web app becomes an Android app via Capacitor or a WebView wrapper, built with Gradle. Run npm run build outside WebContainers first to make sure the production bundle works, then npx cap add android and open the project in Android Studio.

Alternatively, if the app is a solid PWA on your own domain, a Trusted Web Activity is a lightweight option, though it gives you fewer native integrations than Capacitor.

If you prefer not to maintain a Gradle project at all, WebViewGold converts a deployed Bolt web app into native Android and iOS apps without code, with push notifications, deep links and an offline screen configurable. It still has to offer more than the website, because thin wrappers struggle in review, especially under Apple's guideline 4.2.

How do you get through closed testing?

New personal accounts must have at least 12 testers opted into a closed test for 14 consecutive days before requesting production access. Bolt users often build alone, so recruit testers from your community, customers or beta list well before launch.

Push improvements to the closed track during the test using EAS Submit. Google asks how you tested and what you changed when you apply for production.

  • Use a Google Group to manage testers
  • Check that each tester opted in, not just received the invite
  • Log issues and fixes for the production access questions

What Android details do Bolt prototypes miss?

Prototypes rarely handle Android specifics, and testers notice immediately. In Expo, the back button usually works with React Navigation, but custom modals and web views inside the app need explicit handling.

Ask for Android 13+ notification permission at a meaningful moment, configure an adaptive icon and test on a low-end device, where JavaScript-heavy screens feel slow.

  • Adaptive icon foreground and background layers
  • Edge-to-edge status bar and navigation bar handling
  • Remove API keys from the client bundle
  • Google Play Billing for digital goods

How do you fill in Play Console declarations?

Complete Data safety, content rating, target audience, ads and app access before your first production release. Data safety must cover your own backend and every SDK, including Expo modules that touch device data such as location or contacts.

Provide test credentials under app access if login is required, and offer account deletion in the app and via a web link.

What is the fastest way to launch?

Start the closed test early, automate submissions with EAS and polish the listing in parallel. If you want a team to handle the details, neooutput's AI Code Engineers turn Bolt prototypes into production Android apps, and appsubmitter.io helps with store submissions.

Frequently asked questions

Why does EAS Submit fail on my first Android upload?

Google Play requires the first build of a new app to be uploaded manually in Play Console. Upload once by hand, then EAS Submit works through the API.

Do I get an APK or an AAB from EAS?

Production builds default to .aab, which is what Google Play requires. You can configure a separate profile to build APKs for direct device testing.

Can testers use Expo Go instead of the closed test?

No. Google's requirement is about testers opted into a closed testing track on Google Play. Expo Go previews do not count.

Who owns the signing key if EAS creates it?

You do, but it is stored in your Expo account. Download a backup and enable Play App Signing so Google holds the app signing key.

All insights