Bolt.new → App Store & Google Play
Turn your Bolt.new app into a native iOS & Android app
Export your Bolt.new project to GitHub and AppNative turns it into a signed native iOS and Android app — with real native capabilities and automated App Store and Google Play delivery — without porting your Vite + React code to Swift, Kotlin or Expo.
How do you turn a Bolt.new app into a native mobile app?
Export the Bolt.new project to GitHub, connect that repository to AppNative, set your bundle ID, icon and native capabilities, and AppNative generates a signed native iOS and Android shell around your deployed app, builds it in CI, and uploads it to TestFlight and Google Play — no Swift, Kotlin or Expo migration required.
- Starting point
- Bolt.new project exported to GitHub
- Rewrite required
- None — your Vite/React code ships as-is
- Time to first TestFlight build
- Usually under 1 hour
- Platforms produced
- iOS (.ipa) + Android (.aab / .apk)
- Native code you write
- Zero — capabilities are toggles
- Store accounts
- Yours — Apple $99/yr, Google $25 one-time
How to turn a Bolt.new app into a native mobile app, step by step
Six steps, one codebase, no native development. Each step happens inside AppNative except the first.
- 1
Export Bolt.new to GitHub
Use Bolt's GitHub export (or push the downloaded project yourself) so your Vite + React source lives in a repository AppNative can read.
- 2
Deploy your web app
Publish the app to any host — Netlify, Vercel, Cloudflare or your own domain. The native shell renders that live URL, so deployments reach users without a store review.
- 3
Connect the repo to AppNative
Authorize GitHub, choose the repository and branch, and AppNative detects the framework, routes and brand colors automatically.
- 4
Configure identity and branding
Set the app name, bundle ID, icon and splash screen. AppNative generates every iOS and Android asset size, flattens transparency for Apple, and registers the bundle ID for you.
- 5
Turn on native capabilities
Enable push notifications, in-app purchases, Face ID, camera, microphone, location, offline mode, deep links, widgets, Live Activities and Wallet passes — AppNative writes the native code and privacy strings.
- 6
Build and submit
Press Build. AppNative compiles a signed archive on macOS CI, uploads it to TestFlight, and pushes the Android App Bundle to Google Play.
Native capabilities your Bolt.new app gains
These are real native implementations compiled into the binary — not browser fallbacks — and they're what moves an app past Apple's "minimum functionality" bar.
- Push notifications (APNs + FCM) with a REST API, badges, deep links and rich media
- In-app purchases and subscriptions via StoreKit 2 and Google Play Billing
- Face ID / Touch ID biometric app lock
- Camera, photo library, microphone, location and contacts permissions handled natively
- Offline mode with a precached app shell and branded offline screen
- Custom URL scheme deep links (yourapp://) and universal-style routing
- Home-screen widgets and iOS Live Activities
- Apple Wallet and Google Wallet passes
- Native haptics, share sheet and status-bar/safe-area theming
- Persistent login across app restarts, including Google and Apple OAuth
Bolt.new to mobile: the alternatives, compared
Why not migrate the Bolt.new app to Expo or React Native?
Porting to Expo means rebuilding every screen with native primitives and maintaining a second codebase that immediately starts drifting from your web app. AppNative keeps the single Bolt-generated codebase and gives you the native shell, capabilities and store pipeline around it.
Why not stop at a PWA?
PWAs can't be listed in the App Store or Google Play, can't use StoreKit in-app purchases, and lose reliable iOS push, Face ID, widgets, Live Activities and Wallet passes. If your growth or monetization depends on store distribution, a PWA isn't a substitute.
What makes a wrapped Bolt.new app pass App Review?
Apple's guideline 4.2 rejects apps that are just a website in a shell. Passing means shipping native value: push notifications, biometrics, camera use, offline support, widgets or in-app purchases — plus correct privacy usage strings and complete store metadata. AppNative implements all of that and runs a pre-submission check for the usual rejection triggers.
Bolt.new to mobile app: every question, answered
The exact questions people ask before shipping a Bolt.new project to the App Store and Google Play.
How do I turn my Bolt.new app into a mobile app?
Export the Bolt.new project to GitHub, deploy the web app, connect the repository to AppNative, set your bundle ID, icon and native capabilities, add your Apple and Google signing credentials, and press Build. AppNative outputs signed native iOS and Android binaries and uploads them to TestFlight and Google Play.
Can Bolt.new make an iOS or Android app?
Bolt.new generates web projects — typically Vite + React running in the browser. It does not produce a signed iOS or Android binary for store submission. AppNative takes the exported repo and builds that native binary, adding push, purchases, biometrics and offline support.
How do I publish a Bolt.new app to the App Store?
Export to GitHub, deploy the site, then let AppNative generate and sign the native iOS project, register the bundle ID with Apple, upload to TestFlight for testing, and submit through App Store Connect with your screenshots and metadata attached.
Should I convert my Bolt.new app to Expo instead of wrapping it?
An Expo migration means rewriting your Bolt UI with native primitives and maintaining a separate mobile codebase that drifts from the web app. Wrapping keeps one codebase, ships in hours instead of weeks, and still gives you native push, biometrics, widgets and in-app purchases.
Does my Bolt.new app need to be hosted somewhere?
Yes. The native shell renders your deployed web app, so publish it to Netlify, Vercel, Cloudflare Pages or your own host on a stable domain before building. Enabling offline mode then caches the app shell and data so it still opens without a connection.
Can I add push notifications to a Bolt.new app?
Yes. Enable push in AppNative, upload an APNs key and FCM credentials, and send from your backend with one REST call — targeted at a user, a list of users, specific device tokens or everyone, with badges, deep links, custom sounds and images.
Do I need a Mac or Xcode to build a Bolt.new app for iOS?
No. AppNative compiles, signs and uploads the iOS build on hosted macOS runners, so you can ship to the App Store from Windows, Linux or a Chromebook without ever installing Xcode.
Web app to mobile app: key terms defined
- Native app wrapper
- A native app wrapper is a compiled iOS or Android application that renders your existing web app inside a native web view (WKWebView on iOS, WebView on Android) while exposing real device capabilities — push notifications, biometrics, camera, in-app purchases — to that web code through a JavaScript bridge.
- Hybrid app
- A hybrid app ships web technologies (HTML, CSS, JavaScript) inside a native binary that can be distributed through the App Store and Google Play. It differs from a progressive web app, which is installed from the browser and cannot be listed in either store.
- App Store guideline 4.2 (minimum functionality)
- Apple's rule that an app must do more than repackage a website. Apps that add native capability — push notifications, biometric login, camera use, offline support, widgets, in-app purchases — satisfy it; a bare website in a shell does not.
- Bundle ID / package name
- The permanent reverse-domain identifier for your app (for example com.yourcompany.yourapp). It's registered once with Apple and Google and can never be changed for a published app, so it must be decided before your first submission.
- Code signing and provisioning profile
- Apple requires every binary to be signed with a distribution certificate and matched to a provisioning profile tied to your bundle ID and team. Android requires an upload keystore. Without them a build cannot be installed or submitted.
- TestFlight
- Apple's beta distribution service. Uploading a signed build to TestFlight lets up to 100 internal testers install the app immediately, before public App Store review — the fastest way to see your wrapped app on a real device.
- Over-the-air update
- Because a wrapper renders your live web app, deploying your web app updates the mobile experience instantly with no store review. A new native build is only required when something inside the binary changes: icon, splash screen, bundle ID or a native capability.
- StoreKit and Google Play Billing
- The in-app purchase systems Apple and Google require for selling digital goods inside an app. Stripe stays valid on the web, so most apps run both and grant the same entitlement from either payment source.
Bolt.new to mobile app: frequently asked questions
Can a Bolt.new app be published to the App Store?
Yes, once it's compiled into a native binary. Bolt.new outputs a web app, which Apple doesn't accept directly. AppNative generates a signed native iOS app around it, adds native capabilities and uploads it to App Store Connect using your own Apple Developer account.
Do I need to export Bolt.new to GitHub first?
Yes. AppNative builds from a GitHub repository, so use Bolt's GitHub export (or push the project yourself). After that, every rebuild pulls from that repo and branch.
Do I have to rewrite my Bolt.new app in Swift, Kotlin or Expo?
No. Your Vite + React code ships unchanged. Native features are exposed to your JavaScript through the window.AppNative bridge, so you call push, biometrics, camera or purchases with normal JavaScript calls.
How do updates work?
Deploy your web app and users see the change immediately, with no store review, because the native shell renders your live site. You only need a new native build for things baked into the binary: icon, splash screen, bundle ID, or a native capability change.
Can I send push notifications to a Bolt.new app?
Yes. Enable push and upload an APNs key and FCM credentials, then send from your own backend with one REST call — to a single user, a list of users, specific device tokens, or a broadcast, including badge counts, deep links, custom sounds and images.
How do payments work inside the app?
Apple and Google require in-app purchase for digital goods sold in-app, so keep Stripe on the web and use StoreKit/Play Billing in the app. AppNative ships a native paywall plus a purchase bridge, and both paths grant the same entitlement in your database.
Does the app work without internet?
With offline mode enabled, yes. A service worker precaches your app shell and data responses so returning users can open the app and read cached content offline, and a branded offline screen covers a first launch with no connection.
What does it cost to ship a Bolt.new app to the stores?
AppNative is a subscription (see pricing for current tiers) covering unlimited rebuilds. On top of that, Apple's Developer Program is $99/year and Google Play is a one-time $25 fee — both in your name.
Who owns the resulting app?
You do. It's signed with your certificates, published under your developer accounts, and the generated native project lives in your own GitHub repository so you can export or take it over at any time.
Other AI app builders we ship to the stores
Working across builders? AppNative ships Lovable, Base44 and Replit apps to the stores the same way.
Ship your Bolt.new app to the App Store and Google Play
Connect your repo, toggle the native features you need, press Build. Your first TestFlight build can be in testers' hands today — and your Bolt.new workflow doesn't change at all.