How we're using v0 @ Roboto Studio

Hey everybody, thought it might be interesting to share how we’re currently using v0.dev as a studio!

Go read the article

If you want some strong opinions about our perspective, in no particular order:

  • Make sure you’ve grasped the concept of design tokens - these will be everything for context
  • v0 especially works well for headless CMS - page builder type sites
  • You better be building some website tools for organic SEO - e.g mortgage calculators
  • With the additional time you’ve got from scaffolding out components, use it for something valuable for clients, like documentation, resolving more complex business problems etc
  • Smaller teams, with more reliance on v0 are going to far outpace larger teams that don’t embrace AI
  • Feed in theme tokens for better results, and use screenshots to guide v0
  • Vercel is releasing things too god-damn fast, so expect to see a section about “Projects” soon

We’d be happy to answer any questions you have about using AI as a studio!

…Just, please don’t call us an “Agency” :face_vomiting:

Also if you haven’t seen this already, we recommend reading Using v0.dev to build open graph images (and rip off Luma) to hear about how we utilised v0 to build our OG images for our website scaffolding.

7 Likes

Awesome read, @jonoroboto ! Your writing style is so engaging—it really pulls you in. v0 seems like the perfect tool for agencies, and you’ve nailed it by showing how well it works. Seriously, amazing stuff!

Now, if there was a top 10 list of must-have tools for software houses or agencies, I’d bet v0 would be right up there! What do you think?

3 Likes

wait, but you called yourself an agency…

If you haven’t guessed it already, you’re going to see a night and day shift between agencies that are embracing AI and those that aren’t.

ahem.
Since I have your attention, Personally I’m a bit confused about how the concept of a “Block” fits into a project. If I generate multiple components, they’re each a separate Block, so do I have to copy (or import) each of them into my codebase separately? Shouldn’t I just be able to download the whole codebase that v0 is working with, make changes, and then have v0 make more changes?

I was kind of hoping the article would have more on how you’re using it - it mainly says that you are using it and it’s freeing up time for other things. Any other thoughts?

Anyway, thanks for the article, it mainly makes me more excited to figure out how to integrate v0 into my workflow!

1 Like

It would absolutely be at the top for me. There’s literally only 2 ai tools (3 at a push) we use.

  1. v0
  2. Cursor
  3. Raycast

That’s literally enough to easily 3x-4x productivity alone. That’s probably a fairly conservative estimate, because we’ve literally just built an internal app that I didn’t think was possible up until about a week or two ago that uses Gen AI… So by that standard it’s ∞x dev productivity I guess.

1 Like

Wow… Very pedantic, you’ve got my attention.

Okay, so when we’re building websites, we typically build in blocks, like a traditional page builder. Not for all pages, but most, because client’s typically like it the most where it’s “design on rails”. It’s free-form enough you can build what you want, it’s not too abstract that you need a designer onboard to build it. In these cases we typically have:

  • Component
  • Schema
  • All the other files surrounding these two to wire it up

Here’s an example of how it looks within Sanity (this isn’t the best UX, but is ripped directly from our demo)

I was kind of hoping the article would have more on how you’re using it

This is a very good point, and the current office is getting rebuilt… So here’s a massive 17 minute rough cut of me showing exactly how we use v0.dev and Cursor to build a schema. It’s not perfect, and you can watch the pain of me struggling with typescript, but it’s useful as all hell for understanding how it fits into a flow

3 Likes

Incredible, thank you so much! Love to see the rough edges as well as how you’re using the magic.
Seeing how you use Cursor, it might be time for me to give it another try as well.

My advice is, don’t get intimidated by composer and multi file editing. It’s very good, can be destructive, but ⌘ + Shift + S is your friend. It lets you see changes before you accept them by saving the files.

I will say, composer in particular is a little bit wobbly at the moment from my experience, but very valuable.

Also you want to keep an eye out for this feature if you didn’t catch it… This is going to be nuts:

Finally, if you’re working with Sanity make sure you copy and paste this into the cursor config, it’s a slightly outdated config of ours - prompt-engineer-lol · GitHub

All of these thoughts are in no particular order, because brain fried

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.