Dear V0 Management Team,
I’d like to escalate feedback from the community regarding challenges following the transition from V0 Dev → V0 App. A growing number of users are expressing frustration across the forums and external review platforms:
-
Lower quality output and difficulty completing builds.
-
Slower, buggy processing requiring repeated iterations.
-
Excessive credit usage, leaving users feeling penalized for trial and error.
See examples:
As someone who built strong prototypes on V0 Dev, I’ve personally struggled with V0 App. For example, a recent attempt to migrate custom auth to Clerk led to 20+ failed iterations, costing ~$10, despite clear prompting. This highlights how fragile iteration has become and why new/existing users must be guided to the V0 Handbook.
It’s clear the Dev → App transition has been a major change. Removing model access and altering workflows without sufficient onboarding or credit safeguards has understandably caused friction. Many may feel this should have been introduced through a public beta with free credits to gather feedback first.
Recommendations
To address concerns constructively, I suggest:
-
Transparent Communication
-
Publish a blog post acknowledging user frustrations, explaining what’s being improved, and clarifying credit usage.
-
Send a group-wide email linking to the post.
-
Host a video Q&A session to directly address concerns.
-
-
User Support & Retention
-
Provide free credits ($25–50) to all users or those affected by build issues.
-
Reinstate user model selection (e.g., GPT-5, V0 low/medium/high, plus others, pehraps Opus 4.1).
-
Improve iteration guidance by prominently linking the Handbook (example).
-
-
Critical Product Improvements
-
Model Selection: Allow choice between GPT-5 and tiered V0 models.
-
Build Mode Indicator: Show whether in Build (default) vs. Answer/Query mode. Bolt AI does this.
-
Bug Fixing: Users should not pay repeatedly for fixing invalid code. Consider a “Fix Code” option with free or discounted retries.
-
Design Mode: Make all text/image elements fully editable (see Readdy.ai as a strong example).
-
Client Access: Enable restricted client logins for design-only changes, similar to WordPress page builders.
-
-
Long-Term Transparency
-
Publish a public roadmap.
-
Introduce a feedback / feature voting platform such as Featurebase.
-
The V0 community is deeply invested in this platform and eager to use it for upcoming projects. However, the current friction risks negative adoption and reputation. I hope this feedback can be taken seriously, and I’d be glad to provide further detail if useful.
