[Honest Review] One Month with v0: My Real Thoughts After Using It
機械翻訳 / Machine-translated

機械翻訳 / Machine-translated
@aifriends
AI Friends(https://aifriends.jp)のクロスポスト公式アカウント。AIツールの紹介・使い方・できることを、中学生でもわかるやさしい日本語で届けます。
What you'll learn in this article
I needed to quickly build prototypes for websites, and juggling design and code at the same time was becoming a real burden. v0 is made by Vercel, a company I trust, and I'd heard it could automatically generate React code just from text instructions. That was enough for me to give it a try. The fact that there's a free plan made it easy to get started without any commitment. Once I actually tried it and saw how quickly I could turn ideas into something tangible, I was hooked — and kept using it for a full month.
The first week was full of moments of "Wait, it's really this easy?" For example, when I typed "create a login form," a fully designed form appeared within seconds. Even better, I could test it directly in the browser right away, so any gaps between my mental image and the output were immediately obvious. It automatically uses Tailwind CSS, which meant everything displayed cleanly on both mobile and desktop. That said, fine-tuning things like specific colors or small layout adjustments required repeated instructions, which was a bit frustrating at first.
1. Prototype speed is in a league of its own
Just describe your idea in words, and a working UI is ready in under 10 seconds. I was even able to show design concepts on the spot during meetings. Work that would normally take an hour felt like it was done in five minutes.
2. GitHub integration lets you plug it into real projects
A February 2026 update significantly improved GitHub integration, making it possible to add generated code directly to your own projects. From branch creation to deployment, it handles everything automatically — which makes it surprisingly team-friendly.
3. Consistent code quality
Because v0 uses shadcn/ui, a popular component library, the generated code is clean and easy to modify later on your own. I almost never ran into awkward or hard-to-read code patterns.
1. Fine-grained design adjustments don't always cooperate
Instructions like "move the button 5 pixels to the right" often required multiple attempts before being reflected correctly. Results can vary wildly depending on how you phrase your prompt, so trial and error is unavoidable. It's not the right tool if you need pixel-perfect design reproduction.
2. Quality drops with complex functionality
When I tried combining modals, form inputs, and validation into a single complex component, parts of it simply didn't work. Simple UI components are usable as-is about 90% of the time, but that figure drops to around 50% for complex ones — meaning you'll often need to fix things yourself.
3. Tough to scale up to large projects
It can be hard to understand exactly how the generated code works under the hood — it tends to feel like a black box. It's excellent for small-scale prototypes, but for large systems that need long-term maintenance, getting your head around the codebase takes real effort.
I also tried Bolt.new, a similar tool, but I found v0's code quality to be more consistent. Bolt.new is stronger for full-stack development (both frontend and backend), while v0 is purpose-built for UI generation. v0's integration with Vercel is seamless, and being able to deploy with a single click is genuinely convenient. That said, if you want to build both frontend and backend in one go, Bolt.new might be the better fit. v0 works best when you treat it for what it is: a specialist tool for building UI fast.
Recommended for:
Designers and product managers who want to turn ideas into something tangible quickly, startups looking to prototype at speed, and developers already comfortable with React and Tailwind CSS. It's also incredibly useful any time you need to show a "working thing" in a meeting or client pitch.
Not recommended for:
Those who need pixel-perfect design reproduction, people building apps with complex logic, or beginners with no knowledge of React or Tailwind CSS — it may be too steep a curve. It's also not suited for large-scale systems that require long-term maintenance. At the end of the day, this is a tool for prototypes and small projects.
This article is a cross-post from AI Friends.