Quick one for the builders here. During a normal workday, where do you actually capture the most, Figma, your browser, an IDE, Linear, somewhere else? I'm trying to map where the volume is, because where people take screenshots seems to matter more than where they paste them. Curious what your day looks like.

Here at Product Hunt, we found that we were slowly shifting away from @Miro and defaulting to @Notion for typing up brainstorming notes during meetings (we use @Tandem so already have built-in breakout rooms, ambient music options and timers).

So we decided to cancel our Miro account and continue to use Notion or switch to a Figjam board if we really needed a sticky notes format (we're already using Figma so it helps reduce the number of tools we are using). *Spoiler alert: we haven't needed to use a sticky note board yet...

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

I m building landing pages for my next product and exploring AI UI tools that actually help ship faster.

Curious to hear what s working for you from the apps like Lobable or v0

I've tested both and cannot choose what tool is better to buy. Maybe there are better tools?

I recently came across what the majority calls "vibe coding" and I am addicted. As I am a marketing guy, I couldn't resist in creating not one, not two, but 8 apps, which are basically systems to solve my own problems and frustrations.

However, I couldn't help but notice that all these tools are far from perfect. Lovable, Replit (which I use extensively now) say they did something, but in reality, they made only the surface.

I tend to just get an idea, and try to use AI now to get a basic framework. Then after kinda aim to get the core functionality down before moving towards UI and Design...however I often get stuck once it's on UI design as I can never get it the way I like.
As I try to add more features I kinda get lost in the code and then break other things and eventually either abandon the app or simply decide to keep it super simple at the expense of features.
Does anyone have any recs or process that could help in my app making journey? TIA!!

Plan > Prototype > Production > Publish

Hey PH!

Plan > Prototype > Production > Publish

Hey PH!