Skip to content

Your v0 screens are the design.
The iPhone app is next.

v0 gives you Next.js screens on Vercel. AirBuild’s design and engineering agents read them, screen by screen, and build them again with iOS controls.
Same structure, same copy, same hierarchy.

Early access, by invitation from the waitlist.

ledger-studio.vercel.app/invoices

Vercel deployed from your GitHub repository

Keep designing it in v0. AirBuild can sync your changes over automatically.

Same screens, iOS controls.

An example: invoices for a small studio.
  • Data table List rows you can swipe, pull to refresh
  • Dialog Sheet slides up, dismissed by swiping down
  • Tabs Segmented control or one Form section per tab
  • Command menu (⌘K) Search field at the top of the list, as in Mail
  • Dropdown menu Menu from a toolbar button
  • Sidebar navigation Tab bar three to five tabs
What a v0 screen’s parts become. The page you designed keeps its structure and its words; each web control is replaced by the iOS control that does the same job.

What v0 gives you.
A website, and the design.

v0 generates code with Next.js, Tailwind and shadcn/ui, previews it in the browser and deploys it on Vercel: preview deployments for working branches, a production deployment with a stable URL when you publish. With GitHub connected, v0 commits to a working branch, opens a pull request and merges it when you publish.

The result is a website, however app-like the screens look. Some v0 projects connect to a database or an API; others still run on placeholder data. Either is a fine place to start: a backend stays where it is, and placeholders can stay placeholders until you decide.

What to bring.
Just the link.

  1. The deployed address of your v0 project, or the GitHub repository it syncs to.

Read the full guide: v0 to iOS App