Hello Friends of Jo! As you know we recently sunset the old Jo ... but that's because we took the core of it and added in what people said they wanted more > synthetic users to give feedback in addition to real users. And this time around, we've packed this up as a Figma plugin to take this right into workflows where products are designed. We're launching this as Yo today - take it for a spin here: https://www.producthunt.com/prod...
No users? No problem. With Yo, talk to synthetic personas that mirror your target users and get instant feedback on your designs—all inside Figma. Ready for real users? Run quick AI-led interviews without leaving your flow.
Jo, your friendly little user researcher, is officially off-duty for now. She spent her time helping builders get feedback fast, and we've learned so much from everyone who gave her a spin.
Most products fail. Not because they’re bad, but because no one asked users. Jo makes it super simple to get fast, real feedback before you ship. Just share a link. Jo does the rest.
I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:
Write down a simple problem statement: "what am I trying to solve?"
Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"
Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.
I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.
I take the output and paste it into my notes. I then give it to Cursor.
Once in Cursor, I create a new project folder and got at it!
Curious what everyone else does and if you've experience any things to avoid or must do
I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:
Write down a simple problem statement: "what am I trying to solve?"
Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"
Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.
I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.
I take the output and paste it into my notes. I then give it to Cursor.
Once in Cursor, I create a new project folder and got at it!
Curious what everyone else does and if you've experience any things to avoid or must do
OP-ED? Recently I've been finding myself actually buying and downloading apps more than before. The common thread? They're all silly things that almost do nothing. I say almost because what they do offer is a bit of joy during my work day. Some of the recent apps I've purchased or downloaded are @Klack, Googly Eyes, @Docko, @Ball,@TabTab, and @NotchNook. Some of these do have productivity or quality of life improvements (looking at the last two) but others are simply about making the computer fun again. For example @Klack has genuinely made me more focused when I type and I've been able to zone in on work. It's like each clickity-clack is driving me closer to where I want to go and idk, the feedback just feels GOOD. The audio is also really nice, not sure how I can explain it, but feels very high-def for something that is mimicking a tactical feeling. All these apps remind me of a time where shareware and P2P ( @Limewire ) was more popular. Where you might be okay buying a CD or floppy and installing something fun on your computer, then telling (sharing) your buddy about it. And with the rise of vibe coding, I think we're going to see vibeware become a thing. Where users will create something fun, quickly, using AI tools like @Cursor, @Replit, or @bolt.new/@Lovable and then put it at a super low cost or have a free-trial (shareware). Those that don't want to pay, will create their own iteration of it and choose their own distribution method (P2P) but it won't eat at the original. It's my genuine feeling that the internet is about to become fun again (it's already started) and I'm curious if I'm the only one feeling this way and/or embracing it? What do you think? Is the era of vibeware a good thing? And if not why should we refute it? This piece was written with FKJ - Just Piano in the background.
Jo
