# Can Bolt.new Publish to App Store and Google Play? > By Lawrence Arya, Founder & CEO of VP0. Published 2026-06-04. 5 min read. > Source: https://vp0.com/blogs/can-bolt-new-publish-to-app-store-and-google-play Bolt is a browser-based web builder, so reaching the stores takes a wrapping or rebuild step, not a one-click native publish. **TL;DR.** Bolt.new builds web apps, not native binaries, so it cannot publish to the App Store and Google Play directly. Three paths bridge the gap: ship an installable PWA (lists on Google Play via TWA, but not the Apple App Store), wrap the web app in a native shell like Capacitor (watch Apple's thin-wrapper rule), or rebuild the UI in Expo for a real native app. For a true native app, generate React Native from a free VP0 design at $0. The honest answer is: not directly the way a native builder does. [Bolt.new](https://bolt.new/) is a browser-based, full-stack builder focused on web apps, so it does not produce a native iOS or Android binary out of the box. You can still get a Bolt app into the stores, but it takes a wrapping or rebuild step: ship it as an installable PWA, wrap the web app with a native shell, or rebuild the UI in a React Native or Expo project. Below is each path and when to use it. If your real goal is a native mobile app, the cleanest route is to generate React Native from the start, for example from a free [VP0](https://vp0.com) design (the free iOS and React Native design library AI builders read from) in Cursor or Claude Code. ## Why Bolt.new is not a one-click store publish Bolt builds and runs web projects in the browser, which is its strength for sites, dashboards, and web apps. But the App Store and Google Play want native app packages, and a web app is not one. So unlike an Expo-based tool that compiles to a native binary, a Bolt web app needs a bridge to become a store-eligible app. This is a format gap, not a Bolt flaw; it is just the wrong tool if a native binary is the requirement. ## The three real paths to the stores | Path | What it is | Best when | |---|---|---| | PWA | Installable web app, no store needed | You want install without store review | | Native wrapper | Wrap the web app in a shell (Capacitor) | You need a store listing fast | | Rebuild in Expo | Re-create the UI as React Native | You want a real native app | A [Progressive Web App](https://web.dev/explore/progressive-web-apps) installs to the home screen straight from the browser and can list on Google Play via a Trusted Web Activity, though Apple does not accept pure PWAs to the App Store. A native wrapper like [Capacitor](https://capacitorjs.com/) puts the web app inside a native container so it can be submitted, but Apple scrutinizes thin wrappers under its minimum-functionality rule. Rebuilding the UI in [Expo](https://expo.dev/) gives you a genuine native app and the smoothest review. For the iOS-specific fixes people hit, see [the Bolt.new export to iOS App Store fix](/blogs/bolt-new-export-ios-app-store-fix/) and [the Bolt.new React Router Expo mobile fix](/blogs/bolt-new-react-router-expo-mobile-fix/). ## Watch the App Store thin-wrapper rule The risk with wrapping is Apple's review. Its guidelines reject apps that are just a website in a shell with little native value, so a bare wrapper of a Bolt web app can be bounced. If you wrap, add real native capability (offline, notifications, device features) so the app earns its place. Google Play is more permissive about web-backed apps, which is why the PWA-via-Play route is often the faster of the two store paths. ## The cleaner route for a native app If you know you want App Store and Google Play apps, generating React Native from the start avoids the wrapping detour entirely. You get a native binary, the smoothest review, and no thin-wrapper risk. Compare the builders that do this in [can v0.app publish to the App Store and Google Play](/blogs/can-v0-app-publish-to-app-store-and-google-play/) and [can Lovable publish to the App Store and Google Play](/blogs/can-lovable-publish-to-app-store-and-google-play/); for Bolt's plan costs if you stay on the web path, [Bolt.new pricing plans 2026](/blogs/bolt-new-pricing-plans-2026/). ## Key takeaways - Bolt.new builds web apps, so it does not produce a native store binary directly. - Three paths reach the stores: PWA, a native wrapper, or rebuilding in Expo. - Pure PWAs can list on Google Play but not the Apple App Store. - Apple can reject thin web wrappers, so add real native capability if you wrap. - For a true native app, generate React Native from the start, from a free VP0 design at $0. ## Frequently asked questions ### Can Bolt.new publish to the App Store and Google Play? Not directly. Bolt builds web apps, not native binaries, so you reach the stores by shipping a PWA, wrapping the web app in a native shell like Capacitor, or rebuilding the UI in React Native. For a genuine native app with the smoothest review, generate React Native from a free VP0 design, the free iOS and React Native design library for AI builders, at $0. ### Can I turn a Bolt.new web app into a mobile app? Yes, with a bridge step. Make it an installable PWA, wrap it with Capacitor for a store listing, or rebuild the interface in Expo for a real native app. Each trades effort for how native and store-friendly the result is. ### Will Apple accept a wrapped Bolt.new web app? It can, but Apple rejects thin wrappers that are just a website with little native value. If you wrap, add real native functionality like offline support, notifications, or device features so the app passes the minimum-functionality bar. ### Can a Bolt.new app go on Google Play as a PWA? Yes. Google Play accepts Progressive Web Apps via a Trusted Web Activity, so a Bolt PWA can list on Android without a full rebuild. Apple does not accept pure PWAs to the App Store, so iOS still needs a wrapper or a native rebuild. ### What is the best way to get a native app instead of wrapping Bolt? Generate React Native from the start rather than building a web app and wrapping it. Starting from a free VP0 design in Cursor or Claude Code gives you a real native binary, the cleanest store review, and no thin-wrapper risk, at $0 design cost. ## Frequently asked questions ### Can Bolt.new publish to the App Store and Google Play? Not directly. Bolt builds web apps, not native binaries, so you reach the stores by shipping a PWA, wrapping the web app in a native shell like Capacitor, or rebuilding the UI in React Native. For a genuine native app with the smoothest review, generate React Native from a free VP0 design, the free iOS and React Native design library for AI builders, at $0. ### Can I turn a Bolt.new web app into a mobile app? Yes, with a bridge step. Make it an installable PWA, wrap it with Capacitor for a store listing, or rebuild the interface in Expo for a real native app. Each trades effort for how native and store-friendly the result is. ### Will Apple accept a wrapped Bolt.new web app? It can, but Apple rejects thin wrappers that are just a website with little native value. If you wrap, add real native functionality like offline support, notifications, or device features so the app passes the minimum-functionality bar. ### Can a Bolt.new app go on Google Play as a PWA? Yes. Google Play accepts Progressive Web Apps via a Trusted Web Activity, so a Bolt PWA can list on Android without a full rebuild. Apple does not accept pure PWAs to the App Store, so iOS still needs a wrapper or a native rebuild. ### What is the best way to get a native app instead of wrapping Bolt? Generate React Native from the start rather than building a web app and wrapping it. Starting from a free VP0 design in Cursor or Claude Code gives you a real native binary, the cleanest store review, and no thin-wrapper risk, at $0 design cost. --- *Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*