Skip to main content

For v0 builders: no Mac, no Xcode

Turn your v0 app into iOS and Android apps

Export your v0 project, wrap it with Capacitor, and build signed App Store and Google Play apps with Capgo Build. No Mac needed. After launch, changes you make in v0 reach installed apps as live updates.

No Mac
needed for iOS builds
2–3 min
typical native build
Live updates
for changes made in v0

v0 project

Generate the Next.js app with v0. Push it to GitHub so the code lives in a repo.

Export and wrap

Capacitor shell

Build a static out folder and add iOS and Android projects with Capacitor.

Build and update

Capgo release loop

Build signed binaries with Capgo Build, then ship web changes as live updates from GitHub Actions.

The Problem

v0 builds the app. The stores need more.

The app stops at the browser

A v0 project is a web app. Store listings, push notifications, and device features need a native shell around it.

v0 cannot run native tooling

Signing, Xcode, Android Studio, and store uploads happen outside v0. You need the code and a build service.

Every change waits on review

After the first store release, each new version goes back through store review, often 24–48 hours, sometimes much longer.

The stack

What each tool does

v0 builds the web app

Screens, flows, copy, and backend wiring, iterated with prompts. The production build gives you a static out folder to wrap.

Capacitor wraps it

Capacitor puts the built web app into native iOS and Android projects with your app ID, icons, and permissions. The code stays the same.

Capgo builds and updates it

Capgo Build creates signed binaries and uploads them to the stores. Live updates ship later web changes to installed apps.

The Solution

The Capgo path from v0 to the stores

v0 keeps building the product. Capacitor and Capgo add the native build, store upload, and update steps.

Push to GitHub and add a static export

Push the v0 project to GitHub from v0's Git panel (or download the code) and clone it. v0 apps are Next.js, so set output: 'export' in next.config and build to the out folder.

Web app to Capacitor guide

Build it with Capgo Build

Request signed iOS and Android builds from the CLI. iOS builds run on cloud Macs, and a typical build takes 2–3 minutes.

Capgo Build docs

Ship each change as a live update

With the GitHub repo connected, changes you make in v0 push commits to the repo. A GitHub Action builds the app and uploads the bundle, so installed apps get web changes without a new store release.

GitHub Actions integration Live update or native build?

Let your AI agent run releases

The Capgo MCP server lets Claude Code, Codex, or Cursor upload bundles, manage channels, and request builds. Capgo skills add Capgo-specific instructions for the agent.

Capgo MCP server Capgo AI skills

How it works

How v0 builders ship mobile apps with Capgo

From a v0 project to store builds and live updates. You run these commands yourself or let a coding agent run them.

  1. Push to GitHub and add a static export

    Push the v0 project to GitHub from v0's Git panel (or download the code) and clone it. v0 apps are Next.js, so set output: 'export' in next.config and build to the out folder.

    git clone https://github.com/you/your-v0-app.git
cd your-v0-app
npm install
# next.config: output: 'export', images: { unoptimized: true }
npm run build
    Web app to Capacitor guide

  2. Add Capacitor and Capgo

    Add the native projects, then run the Capgo onboarding. It adds your app, creates a production channel, and installs the updater plugin.

    npm install @capacitor/core @capacitor/cli @capacitor/ios @capacitor/android
npx cap init "Your App" com.company.app --web-dir out
npx cap add ios && npx cap add android
npx @capgo/cli@latest init
    CLI onboarding guide

  3. Build signed apps in the cloud

    Set up signing once, then request iOS and Android builds. Signed builds upload to App Store Connect and Google Play for review.

    npx @capgo/cli@latest build init
npx @capgo/cli@latest build request --platform ios
npx @capgo/cli@latest build request --platform android
    Capgo Build docs

  4. Ship each change as a live update

    Add CAPGO_TOKEN as a GitHub secret and a workflow that builds and uploads on push. New plugins or permissions still need a new store build.

    # step in .github/workflows, with CAPGO_TOKEN from secrets
npm ci && npm run build
npx @capgo/cli@latest bundle upload --channel=production --auto-bump
    GitHub Actions integration

AI agent prompt

Let your coding agent do the setup

After you have the v0 code, paste this into a coding agent such as Claude Code, Codex, or Cursor. It installs the Capgo MCP server, adds Capacitor and the updater, and leaves TODOs for signing instead of inventing secrets.

Prompt for your coding agent

I want this project, exported from v0, to become a Capacitor mobile app using Capgo from the start.

Set up the project so an AI agent can use Capgo's MCP release tools through install-mcp:

1. Install the Capgo CLI MCP server for the active AI client. For Codex, run:
   - npx @capgo/cli@latest login
   - npx install-mcp 'npx @capgo/cli@latest mcp' --client codex
   Replace codex with cursor, claude-code, gemini-cli, or windsurf if that is the client this project uses.
2. Read Capgo's MCP metadata when tool details are needed (the hosted server is https://api.capgo.app/mcp):
   - https://capgo.app/.well-known/mcp/server-card.json
   - https://capgo.app/.well-known/agent-skills/capgo-cli-mcp/SKILL.md
   If this client supports agent skills, also run: npx skills add Cap-go/capgo-skills
3. Add a short docs/agent-mobile-release.md file that tells the agent to use the Capgo CLI MCP server as a local stdio server, not a remote HTTP endpoint.
4. Add Capacitor for iOS and Android using the package manager already used by this project.
5. Configure capacitor.config.ts with:
   - appName: the current v0 app name
   - appId: a production-style bundle ID I can edit later, such as com.company.app
   - webDir: the production build output folder (usually out)
   - plugins.CapacitorUpdater.defaultChannel: production
6. Install and configure @capgo/capacitor-updater.
7. Add package scripts for:
   - building the web app
   - syncing Capacitor
   - uploading a production Capgo bundle
   - starting Capgo Build setup for iOS
   - requesting an iOS cloud build
8. Create a first production channel plan:
   - production for users
   - preview for stakeholder review
   - staging for internal testing
9. Keep normal docs and README commands copy-pasteable with npm/npx unless this project already uses another package manager. Keep the Capgo MCP install command exactly as shown above.
10. Do not fake native signing credentials. Leave clear TODOs for the Capgo API key, Apple team details, and bundle ID.
11. After making changes, summarize exactly what changed and what command I should run next.

Apps built with Capacitor

Template and learning products are natural mobile candidates

Creation and learning apps show how web-style flows can become store-ready mobile experiences when packaging, signing, and updates are handled cleanly.

Invitation Maker Card Design app icon EVENTS

Invitation Maker Card Design

Template-driven design flow that maps naturally from responsive web to mobile.

Google Play installs
20.0M
Store rating
4.6
Infinite Japanese app icon Educational

Infinite Japanese

Focused learning app where small lesson and onboarding improvements compound.

Google Play installs
1.8M
Store rating
4.6
StudySmarter - School & uni app icon EDUCATION

StudySmarter - School & uni

Study workflow where web product iteration can continue after app packaging.

Google Play installs
6.5M
Store rating
4.8

Customer proof

What teams shipping with Capgo say

5.0/5 rated by developer teams 9,400+ teams Read reviews

sikafanka

Design, radius 5

“Capgo Build helped us simplify our Capacitor app release process. We can build and ship iOS and Android apps from one clear workflow.”

Kapil

Founder, NuTriQ

“Being able to push production OTA updates instantly without waiting for full App Store review cycles has been a massive operational advantage.”

Portrait of Luis Dominguez

Luis Dominguez

El que paga, Anirol

“Since I started using Capgo everything is faster, and I can give my users the time they deserve without neglecting my daily life.”

FAQ

Questions v0 builders ask

Short answers for taking a v0 app to the App Store and Google Play.

Can v0 publish straight to the App Store?

No. v0 builds the web app. You export the code, wrap it with Capacitor, and build signed iOS and Android apps with Capgo Build, which uploads them to App Store Connect and Google Play.

Web app to Capacitor guide

Do I need a Mac or Xcode?

No. Capgo Build runs iOS builds on cloud Mac machines. You still need an Apple Developer account for the App Store and a Google Play developer account for Android.

Capgo Build docs

My v0 app uses server actions or API routes. Does it work?

The mobile app ships the static export only. Keep server code deployed on Vercel and call it with its full https URL from the app. Pages and client components work as they are.

Next.js with Capacitor

Do shadcn/ui components work on mobile?

Yes. They are React components with Tailwind styles, so they render in the native web view like in a browser. Check touch targets and safe areas on a real device.

Will changes I make in v0 reach the mobile app?

With the GitHub repo connected, changes you make in v0 push commits to the repo. Yes, for web-layer changes. A GitHub Action runs bundle upload on each push, and installed apps download the update. New plugins or permissions still need a new store build.

GitHub Actions integration

Can my AI agent handle the release steps?

Yes. npx @capgo/cli mcp starts a local MCP server that Claude Code, Codex, or Cursor can use to upload bundles, manage channels, and request builds. Capgo skills add Capgo-specific instructions for the agent.

Capgo MCP server

Put your v0 app in the stores

Start the 14-day free trial, export your v0 project, and request your first iOS and Android builds from the CLI.