Publish a Bolt.new App to the App Store: Web Project or Expo?

How to get a Bolt.new app into the Apple App Store, depending on whether you built a web project or an Expo mobile project, plus review and signing tips.

Short answer

The right path for a Bolt.new app depends on what Bolt generated. A web project (React, Vite, Next.js and similar) is deployed first and then wrapped in a native iOS shell such as WebViewGold; an Expo project is already React Native and goes through an iOS build and signing pipeline. In both cases Apple expects real native value and a complete, tested app.

On this page
  1. First question: which kind of Bolt project do you have?
  2. Path A: a Bolt web project
  3. Path B: a Bolt Expo project
  4. Review risks specific to Bolt apps
  5. Submission and after
  6. FAQ
  7. Tools from the jocapps ecosystem

First question: which kind of Bolt project do you have?

Bolt.new runs a full development environment in the browser and can scaffold many stacks. For the App Store, two families matter:

  • Web projects. React with Vite, Next.js, Astro, Svelte and similar. Bolt previews them in its in-browser environment and can deploy them to a hosting provider, commonly Netlify, or you download the code or push it to GitHub.
  • Mobile projects using Expo. Bolt can start projects from Expo, which is React Native. You preview them on a phone through Expo tooling, and they can be compiled into a real iOS binary.

Open your package.json. If you see expo and react-native, you are on the mobile path. If you see vite, next or similar without React Native, you are on the web path. The rest of this article splits accordingly.

Path A: a Bolt web project

Get it out of the preview

The Bolt preview runs inside your browser tab. It is not a production server, and an iOS app cannot point at it. Deploy the project to a stable host with a custom domain. Our guide on deploying a Bolt.new app to production covers environment variables, Supabase keys and the build settings that typically need fixing after export.

Wrap the deployed URL

WebViewGold turns your deployed Bolt app into an Xcode project: insert the URL, set name, icon, splash screen and bundle ID, and enable native features. You build and sign in Xcode with your own Apple developer account. Because the shell loads the live site, every Netlify deploy updates the app's content without a new store release.

Settings that matter for Bolt web apps:

  • Client-side routing. Vite single-page apps rely on the host rewriting unknown paths to index.html. If deep links or refreshes show a 404 on the web, they will also fail in the app. Fix the redirect rule on the host first.
  • Environment variables. Bolt projects often reference VITE_ variables. Missing variables in the production build produce a blank screen, which is the fastest way to a rejection.
  • Viewport. Check that inputs do not zoom on focus (font sizes of at least 16 px on inputs avoid it) and that fixed bottom bars respect the home indicator.

If you would rather hand over the Xcode part, WeSetupYourWebViewApp builds the WebViewGold app for you with full source code in about 72 hours.

Add native reasons to exist

A deployed Bolt app inside a frame is exactly what Apple Guideline 4.2 targets. Choose two or three native features that fit your product:

Product typeNative features that make sense
Booking or schedulingPush reminders, calendar export, deep links from notifications
Field or inspection toolCamera capture, offline queue, haptic confirmation
Community or chatPush for replies, native share, Sign in with Apple
Internal company toolFace ID unlock, push approvals, MDM-friendly configuration

Most of these are configuration options in WebViewGold rather than custom Swift code, which keeps the native layer small and leaves product logic in your Bolt codebase.

Path B: a Bolt Expo project

An Expo project is already a React Native app, so you skip the wrapper. Instead you need a reliable build and signing pipeline.

  1. Move the code out of the browser. Push to GitHub or download it. Run it locally with Node and the Expo CLI to confirm it builds outside Bolt.
  2. Check the app config. In app.json or app.config.js, set the iOS bundleIdentifier, version, build number, icon and splash assets. Add usage descriptions for every permission the app requests.
  3. Build for iOS. Expo's cloud build service (EAS Build) can produce a signed iOS build without a local Mac, using credentials from your Apple developer account. Alternatively, generate the native iOS project and build in Xcode.
  4. Distribute through TestFlight. Upload the build and test with real users. Expo projects that worked in a development client can still crash in release builds, often due to missing environment variables or native modules not included in the build.
  5. Submit. Upload to App Store Connect and complete the listing.

Bolt-generated Expo code is a good start but rarely production-ready. Typical gaps: no error boundaries, API keys embedded in the client, no handling for slow networks, and navigation that breaks on Android back gestures. If you need ongoing help with a React Native codebase, apprat.io combines AI-assisted development with human developer hours for building and maintaining iOS and Android apps.

Review risks specific to Bolt apps

Secrets in the bundle. Bolt makes it easy to call third-party APIs straight from the front end. In a web app this exposes keys in the browser; in a mobile app it ships them inside the binary. Move calls that need secret keys to a server function before submitting.

Demo data left in. Seed data that looked useful during prototyping (fake users, sample orders) confuses reviewers and can count as misleading content.

Incomplete flows. A "Forgot password" link that leads nowhere or a settings page with dead toggles signals an unfinished app under Guideline 2.1.

Login and account deletion. Provide a reviewer account and an in-app way to delete accounts if users can sign up.

Submission and after

Whichever path you took, the App Store Connect steps are the same: app record, privacy details, screenshots for the required device sizes, review notes, then submission. Plan a TestFlight round first; our article on TestFlight and Play Console internal testing explains how to structure it.

appsubmitter.io takes care of submissions, listings, CI/CD and rejection handling in your own accounts. If you are still choosing between builders, our comparison of Lovable, Base44 and Bolt looks at how each one reaches the stores.

FAQ

Can Bolt.new publish directly to the App Store?

Bolt does not submit apps to Apple for you. A web project needs a native shell built in Xcode; an Expo project needs an iOS build, signed with your Apple developer account, then uploaded to App Store Connect.

Should I rebuild my Bolt web app in Expo to get into the App Store?

Only if you need deep device features or heavy offline use. A well-built web app in a native shell with push notifications and other native features is faster to ship and easier to maintain.

Do I need a Mac to publish a Bolt app to the App Store?

For the wrapper route you need Xcode, which runs on macOS, or a service that builds for you. For Expo projects, cloud build services can produce the iOS build, but a Mac remains useful for debugging.

Why does my Bolt app show a blank screen on iPhone?

Usually missing production environment variables, a failed API call on start, or a routing rule missing on the host. Open the deployed URL in Safari on the phone first; if it fails there, fix the web deployment before touching the app.

Tools from the jocapps ecosystem

Want this done right, and fast?

Talk to our AI Code Engineers and AI architects. In a free 30-minute call we look at your idea, prototype or roadmap and tell you honestly what it takes to ship it.

24/7 call support in English and German.

Free call

Free intro call

Tell us which task an AI agent should take responsibility for. We show how our platform, AI Code Engineers and operations plug into your stack.

  • 30 minutes, no obligation
  • Honest feasibility check
  • Concrete next step
Rather talk now? 24/7 call support in English and German+49 761 519 751 50