Yes, you can publish a vibe-coded app to the App Store and Google Play. "Vibe coding" tools such as Lovable, Bolt, Replit, v0, Cursor, Base44, and Claude Code almost always output a web app, not a store-ready binary. To reach the App Store or Google Play you keep that web app as the source of truth and add a native release layer around it, either by hand with Capacitor or Expo, or in minutes with a packaging tool like WebNativeApp.
The short answer: vibe coding builds the product, not the store listing.
Vibe coding describes prompting an AI tool to generate a working app instead of writing the code yourself. It is a build method, not a distribution channel. Apple and Google still require a signed native project, an app identity, store assets, and a review submission, none of which the prompt itself produces.
Vibe coding gives you the product
Tools like Lovable, Bolt, Replit, v0, Cursor, Base44, and Claude Code can generate a full web app, including auth, a database, and payments, from a prompt.
The stores need a native project
App Store Connect and Google Play both require a signed iOS or Android build, not a website URL, no matter how the website was built.
A packaging step connects the two
Capacitor, Expo, or a hosted tool such as WebNativeApp turns the vibe-coded web app into that signed native project without a rewrite.
A handful of vibe coding tools, including some Bolt and Base44 projects started as "mobile app" prompts, generate an Expo codebase instead of a website. Check what your tool actually produced before choosing a packaging route: an Expo project follows Expo's own build and submit workflow, while a web app needs the native-shell route below.
How to publish a vibe-coded app, in order.
This sequence works no matter which vibe coding tool built the product, because every route ends at the same two requirements: a stable web app and a signed native build.
- Confirm the tool actually built a web app: Most vibe coding tools default to a website. Open the live preview and check it loads as a normal URL, not a native-only Expo project.
- Publish to a production domain: Deploy to a real HTTPS URL with working routes, auth, and APIs, not a temporary preview link tied to the builder.
- Test the mobile experience: Check layout, tap targets, keyboard behavior, and loading, empty, and error states at phone width, since the native shell inherits whatever the web app already does.
- Add the native release layer: Package the live URL with Capacitor by hand, or paste it into WebNativeApp to generate a signed iOS and Android project with an app icon, splash screen, and native identity.
- Prepare store accounts and assets: Apple Developer Program and Google Play Console access, plus a name, icon, screenshots, category, and privacy details for each store.
- Test the real build: Run the packaged app on physical devices or through TestFlight and a Google Play testing track before requesting review.
- Submit and keep shipping: Send the build to App Review and Google Play review. Future prompts in your vibe coding tool update the live web app, which reaches the installed app without a new native build.
Where popular vibe coding tools actually land.
Every tool below can produce a real product. The difference is what comes out the other end, and which packaging route gets it to the stores.
| Tool | Typical output | Path to the stores | Dedicated guide |
|---|---|---|---|
| Lovable | Web app | Native shell (Capacitor or WebNativeApp) | Lovable to App Store |
| Bolt | Web app, or Expo if chosen at the start | Native shell for web output; EAS for Expo output | Bolt to App Store |
| Replit | Web app | Native shell (Capacitor or WebNativeApp) | Replit to mobile app |
| v0 | Web app | Native shell (Capacitor or WebNativeApp) | v0 to App Store |
| Cursor | Web app (code you direct) | Native shell (Capacitor or WebNativeApp) | Cursor to mobile app |
| Claude Code | Web app (code you direct) | Native shell (Capacitor or WebNativeApp) | Claude Code to mobile app |
| Base44 | Web app, or Expo if chosen at the start | Native shell for web output; EAS for Expo output | Base44 to mobile app |
| Bubble | Web app | Native shell (Capacitor or WebNativeApp) | Bubble to App Store |
What to have ready before you package a vibe-coded app.
Vibe-coded app readiness
- A stable production URL, not a builder preview link.
- Working auth, database, and payment flows outside the builder sandbox.
- A mobile-tested layout, with real loading, empty, and error states.
- Links, redirects, and OAuth callbacks that behave inside a native shell.
Store readiness
- Apple Developer Program and Google Play Console access.
- App name, icon, splash screen, category, and screenshots.
- Public privacy policy and support URL.
- Accurate privacy answers and a demo account when login is required.
Official publishing resources.
Vibe coding to mobile app, answered
What is vibe coding?
Vibe coding is building software by prompting an AI tool in natural language instead of writing the code by hand. Tools such as Lovable, Bolt, Replit, v0, Cursor, and Claude Code generate the product from that conversation, usually as a working web app.
Can a vibe-coded app go on the App Store and Google Play?
Yes. Most vibe coding tools produce a web app, which needs a native release layer before either store will accept it. Adding that layer with Capacitor or WebNativeApp does not require rebuilding the product.
Do I need to rewrite my vibe-coded app in Swift, Kotlin, or React Native?
No, unless the product depends on native-only screens or performance a web app cannot deliver. Most vibe-coded products can reach both stores by packaging the existing web app rather than rebuilding it natively.
Will Apple or Google reject an app because it was vibe-coded?
No. Apple and Google review the finished product, not the tool that built it. A vibe-coded app is judged the same way as any other submission: it needs to be stable, useful beyond a thin wrapper, and compliant with each store's policies.
Which vibe coding tool is best if I plan to publish to mobile?
Any tool that produces a real, stable web app works, including Lovable, Bolt, Replit, v0, Cursor, and Claude Code. The packaging step is the same regardless of which one you choose, so pick based on how you prefer to build, not on store compatibility.
How much does it cost to publish a vibe-coded app to both stores?
Packaging an existing web app with WebNativeApp costs $29 for one platform or $49 for both, one-time, on top of your vibe coding tool's own plan and each store's developer account fee.
More on shipping a vibe-coded app to mobile.
Turn your vibe-coded app into a mobile app.
Paste the production URL of the app you already vibe-coded. WebNativeApp checks it, prepares a signed iOS and Android project, and lets you keep shipping from the same tool you used to build it.