What is our primary use case?
My main use case for v0 is to build MVPs and prototypes for applications and full stack applications in Next.js, and I have also used v0 for building a mobile app which was based on React Native.
I built a school management ERP for schools in India using v0, and I created a web app version for it, a very minimal prototype with basic essential back-end APIs. I also built a mobile app version for the same, which was in React Native.
Regarding my main use case with v0, I have published and connected my GitHub to the v0 account and v0 AI, which provides one million tokens on the Hobby tier and ten million edge cases and CDN networks, and also provides some CI/CD as well. I have also built some blog applications as well as some tools and web apps using Next.js and v0's AI.
What is most valuable?
v0 stands out because it is very seamless when I have to deploy a Next.js application, which is really good. Although publishing a Next.js application requires going through more steps, v0 makes it very easy and simple. It builds the project on its own and also provides some CI/CD if I connect my GitHub to it, meaning I just need to write my code and push it to the main branch, and then it will automatically deploy it to production, and the CI/CD is actually really good.
These features are essential for me as I'm a programmer with very minimal experience in deployment and strategies and building the whole DevOps pipeline infrastructure for deploying an application and scaling it. The Hobby tier is actually really good as it provides one million tokens on a Hobby tier and is very seamless and easy, along with being very quick. This took a lot of headache off my mind when I had to do deployment work.
It also provides a very easy, seamless experience in adding my own DNS and my own domain into my projects, making them live.
v0 AI is actually very impactful, as it has increased production, building of products, and has made things very quick. Developers no longer have to code from scratch and do not have to build the application from scratch; they can just use v0, give it a prompt, and v0 now has Opus incorporated in it, which is a really good thing, as Opus is very good in performance and building good and amazing, beautiful UIs.
What needs improvement?
The updates that v0 has added in its policies and terms and conditions were needed because v0 used to push directly into the main branch, which was not good. The service has now improved, making a separate branch and generating a pull request that the repo owner has to accept before the changes get put to the main production branch. However, this poses complications for older projects that are already hosted on v0, as they now need to configure and update their whole structure due to the change in branch pushing methodology.
The build errors can actually give a big headache to the developer because v0 has no way to resolve them. On a scale of one to ten, I would rate v0 overall in a very favorable way while stating it should allow developers to push code to the main branch directly and not allow v0 to push to the main branch.
v0 has helped me a lot, and I would give it a score of eight because it still needs some improvement and could go a good way. I feel more confident about free features, making it a big help for developers due to many options available in the market now.
I chose eight out of ten because it is really good, offering a big free tier with a huge one million requests on its Hobby tier which can actually make an application live for about more than a year or two if it has minimal traffic, as one million requests is too much for a very beginner-friendly project. I deducted two points because it does not allow me in a few projects to push directly to the main branch as my GitHub CI/CD does not permit it, and Vercel revokes the chunk of code I'm pushing, stating I no longer have the authority, which is a really bad bug needing improvement. Additionally, the Hobby tier does not recharge each month, which is also a downside.
For how long have I used the solution?
I have been using v0 for the last one year, approximately one to one and a half years.
What do I think about the stability of the solution?
I had a lot of issues with v0 because it was very unstable, as the AI used to bug out, just stopping responses entirely. I often had to change chats and retrieve the content for a particular chat. Although v0 provides a forking feature that is very good, it was not functioning properly, leading to reliability issues. A particular deployment encounter where I needed to fix the preview rendered my browser unstable, crashing repeatedly when I used the preview option.
What do I think about the scalability of the solution?
I do not think that I have to scale the application, so I have not tested v0's scalability yet.
I have not scaled any application using v0, as I have not received that much traffic. Once I do, I will find out how it performs.
How are customer service and support?
I did not contact any customer support for v0, as the AI was sufficient for me to figure things out on my own.
Which solution did I use previously and why did I switch?
Before v0, I was using Lobe or had used Netlify, but v0 provides more features than Netlify because Lobe's AI would hallucinate a lot and does not grant access to more models like Claude or Sonnet, which are essential for constructing modern UIs and adding more features. v0 provided the model called Opus, which is from Claude and performed very well compared to other agents, which is why I chose v0 over others, including previous usage of Replit.
How was the initial setup?
My experience with setup cost, pricing, and licensing for v0 is that it can be a little bit tricky for a beginner because it becomes very costly. If someone has to scale their product and is already making money with the Hobby tier, they should go for the paid version, which is not a very bad thing about the payment. Pricing is pretty neutral, not that bad, but the setup cost and all the associated expenses if added up can actually cost more than other services like Netlify or GCP, so I believe they need to work on it.
What about the implementation team?
I mostly work alone, so I utilize v0's powers to build my applications, add features and changes, and make them production-ready. I handle code reviews and all tasks independently, making it a significant money-saving and time-saving method since no additional employees are needed. v0 also offers an option to download the entire file and upload a zip file directly containing all my files and folders, enabling me to start working on a new chat if the AI is hallucinating, which is a really good feature. I have not seen any return on investment currently, as my projects are still hosted there and scaling is not on my immediate agenda.
What was our ROI?
I have not seen any return on investment currently, as my projects are still hosted there and scaling is not on my immediate agenda.
What's my experience with pricing, setup cost, and licensing?
My experience with setup cost, pricing, and licensing for v0 is that it can be a little bit tricky for a beginner because it becomes very costly. If someone has to scale their product and is already making money with the Hobby tier, they should go for the paid version, which is not a very bad thing about the payment. Pricing is pretty neutral, not that bad, but the setup cost and all the associated expenses if added up can actually cost more than other services like Netlify or GCP, so I believe they need to work on it.
Which other solutions did I evaluate?
I evaluated other options such as Replit, Google AI Studio, Firebase Studio, Claude artifacts, Gemini, Lobe, and Page-44, finding that while they had their good and bad points, v0 offers a more seamless and easy experience. I have been very familiar with v0 since I have been working with it for some time, and it helps give me about more than five to six thousand lines of code, which no other AI literally provides, and that is really amazing.
What other advice do I have?
The estimate is that I can build and deploy applications in weeks rather than months, which is a really good thing and very quick.
The advice I would give others looking into using v0 is that they should provide better prompts and ensure their libraries and packages are updated, as v0 will not accept outdated content and packages. For example, Vercel does not allow adding a New.js 15 based application since it was elected recently; I have to upgrade the packages. This is good for keeping everything updated, and v0 is also very fast, quick, and reliable, making it easier to work with now. I have given v0 an overall rating of eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?