Absolutely! This article really hits home with the struggles of AI prototyping tools. I was just thinking about how well it connects with some thoughts I shared recently.
The component-level approach mentioned here completely aligns with what I've been exploring in my recent blog post about building apps with AI. If you're wrestling with that 50-60% completion barrier in AI prototyping, you might find some practical insights in my late-night coding adventure where I built an entire app for just $4.25: https://thoughts.jock.pl/p/building-apps-with-ai-2025-late-night-coding-adventure
What I found fascinating is how breaking things down into manageable components not only makes the AI work better, but actually gives you more control over the final result. It's that balance between letting AI handle the tedious parts while you focus on the creative direction that makes these tools genuinely useful instead of just novelties.
Those shadcn resources are gold too! I've been experimenting with different frameworks for quick builds, and having a consistent component library makes everything so much smoother.
The documentation point is crucial as well - I've definitely learned (sometimes the hard way!) that keeping track of what works across different AI tools saves countless hours of frustration.
Thanks for sharing this fantastic breakdown of practical V0 techniques!
I've spent most of time using Replit and now on Cursor. Haven't really deep dive on v0. But some things that make v0 stands out are revising components (guess this is the new feature!) and pull components from shadcn/ui.
This puts v0 super strong on creating frontend than any other competitors!
Will share some things using Replit and Cursor in sometime.
I see. It's not there on Replit last time I checked. But I guess the direction is supposed to go there, if not, it's going to be harder to change specific components using only chat or vibe-coding.
Absolutely! This article really hits home with the struggles of AI prototyping tools. I was just thinking about how well it connects with some thoughts I shared recently.
The component-level approach mentioned here completely aligns with what I've been exploring in my recent blog post about building apps with AI. If you're wrestling with that 50-60% completion barrier in AI prototyping, you might find some practical insights in my late-night coding adventure where I built an entire app for just $4.25: https://thoughts.jock.pl/p/building-apps-with-ai-2025-late-night-coding-adventure
What I found fascinating is how breaking things down into manageable components not only makes the AI work better, but actually gives you more control over the final result. It's that balance between letting AI handle the tedious parts while you focus on the creative direction that makes these tools genuinely useful instead of just novelties.
Those shadcn resources are gold too! I've been experimenting with different frameworks for quick builds, and having a consistent component library makes everything so much smoother.
The documentation point is crucial as well - I've definitely learned (sometimes the hard way!) that keeping track of what works across different AI tools saves countless hours of frustration.
Thanks for sharing this fantastic breakdown of practical V0 techniques!
Thanks for the comment, Pawel. I'm excited that you've been actively exploring in this space too. Love it.
I've only tried Replit several times, while using Cursor a bit more often.
Did you run a comparison between tools similar to Vercel? I'd be curious to know that you think
Thanks for the message.
I did. I just haven't got time to share my most recent thoughts yet.
That said, I ran a similar comparison test a while ago: https://designwithai.substack.com/p/i-ran-the-same-prompt-through-three-ai-prototyping-tools
This is amazing, it’s interesting to see how your prompt “sounds” like a UI designer. Shall try this structure and share results soon :)
Curious to hear your experience!
Thanks for sharing this!
I've spent most of time using Replit and now on Cursor. Haven't really deep dive on v0. But some things that make v0 stands out are revising components (guess this is the new feature!) and pull components from shadcn/ui.
This puts v0 super strong on creating frontend than any other competitors!
Thanks! It's amazing that you've been actively using Replit and Cursor. Would love to hear more about your experience sometime.
Btw, that "select and revise" feature has become common in other tools like Lovable and Bolt too.
Will share some things using Replit and Cursor in sometime.
I see. It's not there on Replit last time I checked. But I guess the direction is supposed to go there, if not, it's going to be harder to change specific components using only chat or vibe-coding.