v0 by Vercel

@fmerian Congrats on the launch! How do you measure success for v0? Is it developer productivity, deployment frequency, user retention, or something else?

@kaansoral good q. with this update, you can now:

• Work on existing codebases: import any @GitHub repo or @Vercel project, create branches with new chats, and open pull requests all from inside v0

• Use any framework: @Svelte, @Astro, @Vite, @Nuxt, etc.

• Build full-stack applications and agents

Full details in this thread (edited)

anyone can built with @v0 by Vercel

from the blog announcement (source):

• Product leaders turn PRDs into prototypes, and prototypes into PRs, shipping the right features, fast. They go from "tell sales there's another delay" to "it's shipped."

• Designers work against real code, refining layouts, tweaking components, and previewing production with each update. They go from "another ticket for frontend" to "it's shipped."

• Marketers turn ideas into site updates immediately, edit landing pages, changing images, fixing copy, and publishing, all without opening a ticket. They go from "please, it's a quick change" to "it's shipped."

• Engineers unblock stakeholders without breaking prod, making quick fixes, importing repos, and letting business users open PRs, all in a single tab. They go from "I can't keep up with the backlog" to "it's shipped."

• Data teams ship dashboards the business actually uses, building custom reports and analytics on top of real data with just a few prompts. They go from "that's buried in a notebook" to "it's shipped."

• GTM teams close deals with the demo customers actually asked for, create live previews, mock data, and branded experiences in minutes. They go from "let's show the standard deck" to "it's shipped."

FYI you can read what's new in this blog announcement and ICYMI you can also find the latest product updates in /p/v0 - hope it clarifies!