Skip to main content

Publishing a Bolt.new App on the App Store and Play Store

By the OnlineAppCreator editorial team4 min read

Short answer

A Bolt.new project reaches the App Store and Google Play by one of two routes: deploy the web app and package it in a native shell, or build a mobile project with Expo and compile it with Expo's build tooling. For web projects, a configured native shell is usually the fastest route, and a done-for-you service can deliver store-ready iOS and Android apps within 72 hours.

On this page
  1. Identify what Bolt built
  2. Route one: web app plus native shell
  3. Route two: Expo project and native builds
  4. Accounts and requirements on both stores
  5. Common Bolt-specific pitfalls
  6. Checklist before you submit

Bolt.new runs a full development environment in the browser, which makes it a quick way to generate and iterate on full-stack web apps and, increasingly, mobile projects. That flexibility means there is no single path to the stores. What you do depends on what Bolt generated for you. This article helps you identify which kind of project you have, choose the matching route and avoid the deployment gaps that often appear between "it works in the Bolt preview" and "it is live in the App Store".

Identify what Bolt built

Open the project files and check the framework. Most Bolt projects are web apps built with React, Vite, Next.js or similar, deployed to a hosting provider through Bolt's integrations. Some are Expo projects using React Native, created when you asked Bolt for a mobile app. The two require different publishing paths. Web projects produce HTML, CSS and JavaScript that a browser or WebView runs. Expo projects produce JavaScript for React Native and must be compiled into native binaries.

Route one: web app plus native shell

For a Bolt web app, first make it production ready. The Bolt preview runs inside the browser, so test the deployed version on a real domain, check environment variables, confirm database connections work outside the preview and make sure routes load directly. Then package the deployed URL in a native iOS and Android project.

You can do that yourself with WebViewGold, which converts a website or web app into native iOS, Android and macOS apps with push notifications, biometric authentication, in-app purchases, an offline screen and deep links. If you would rather not open Xcode and Android Studio at all, We Set Up Your WebView App configures the apps for you and delivers your personal iOS and Android apps within 72 hours, with an App Store and Google Play approval guarantee or your money back.

The advantage of this route is that you keep iterating in Bolt. Every redeploy updates the apps without a new store submission, unless you change native behavior.

Route two: Expo project and native builds

If Bolt generated an Expo app, the path runs through Expo's build service or a local native build. You export the project, configure app.json or app.config.js with bundle identifier, package name, icons and permissions, then create iOS and Android builds and submit them. This produces a true React Native app with native UI components, which helps with Apple's minimum functionality expectations. The trade-off is more setup, dependency management and native debugging, and every code change requires a new build or an over-the-air update mechanism.

Choose this route if the app relies on native components or device APIs heavily, or if your team is ready to maintain a mobile codebase. Choose the shell route if the web app already works well on phones and you want both stores quickly.

Accounts and requirements on both stores

Regardless of route, you need an Apple Developer Program membership (USD 99 per year) and a Google Play developer account (one-time USD 25). Enroll as an organization if the app belongs to a company. New personal Google Play accounts currently must run a closed test with at least 12 testers for 14 days before production, which we explain in our closed testing guide.

Both stores require a privacy policy, a description of the data you collect, Apple's App Privacy answers and privacy manifest, and Google's Data safety form. If users can create accounts, they must be able to delete them in the app. Bolt can generate these screens quickly, but test that deletion actually removes data in your database.

Common Bolt-specific pitfalls

Several issues show up repeatedly with Bolt projects. Secrets and API keys end up in frontend code because the preview made it convenient; move them to server-side functions before you publish. Database row-level security is left open during prototyping; lock it down before real users arrive. Large bundles from many dependencies slow down the first load inside a WebView, which reviewers notice. And OAuth providers that worked in the preview fail in the native app because redirect URLs were never set for the production domain.

Another frequent problem is the start screen. If your Bolt project began as a landing page with a "Get started" button, configure the app to open directly in the product. A marketing homepage inside an app is one of the fastest routes to a Guideline 4.2 rejection.

Checklist before you submit

  1. Deployed production URL with HTTPS and your own domain.
  2. Secrets moved server-side, database access rules enforced.
  3. Login tested on a real phone, including password reset links.
  4. Account deletion in the app.
  5. At least two native features enabled and connected to real user needs.
  6. Demo account with sample data and clear review notes.
  7. Listings, screenshots and privacy answers prepared for both stores.

For listing details, use our App Store listing checklist. If a Bolt prototype is turning into a product that needs a proper architecture, team and roadmap, that transition from prototype to operating product is the kind of work our company building practice takes on.

Frequently asked questions

Can Bolt.new publish directly to the App Store?

Bolt generates and deploys the code, but submission still runs through App Store Connect and the Play Console under your own developer accounts, using either a native shell or an Expo build.

Should I use the Expo route or a web wrapper for my Bolt app?

Use Expo if the project is already a React Native app or needs heavy native functionality. Use a native shell if you have a web app that works well on phones and you want both stores quickly.

Do I have to resubmit my Bolt app after every change?

With a native shell, web changes appear automatically after you redeploy. Expo apps need a new build or an over-the-air update for code changes.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.