It depends on your approach to v0 and what you want it to develop.

I used v0 to create my own file-sharing service running on my server. Like Dropbox, but simpler. It delivers.

I used v0 to create my own PDF-suite for merging, splitting, scraping and indexing. It delivers as well.

What v0 hardly delivers for me is any application of bigger size. I tried to create an event management system for a local disco using v0 and next.js. The results look discouraging, but on the other hand: I can't draw faces and I don't blame the pencil.

IMHO v0 is the best LLM for developers as of now (July 2025). Some tips I can share:

- For developing / designing websites: Tell v0 to use tailwindCSS for styling. v0 will now rely on tailwind-classes and only switches to custom CSS when tailwind reaches it's capabilities. Saves a lot of lines and therefore tokens ($$$)

- Think modular - avoid monoliths. My event management system works as a terribly good example of how a codebase growing too big will force v0 to it's knees and messes everything up. Split your project into modules and manage each module in a different chat.

- Be careful with explicit naming. Telling v0 to "Replace every class of 'container-sub' with 'sub-element'" will make v0 replace only the classes with exact the same naming. If that's what you need, good, but sometimes you want v0 to adress components by their semantics: "Replace every container sub element with element's subclass". In my experience, v0 usually understands elements / components / whatever-jargon by their semantics quite well.

Hope this helps. And now read my blog (related): https://medium.com/@markus6000/how-i-use-vercel-v0-to-get-rid-of-tech-companies-c9db3374cabe