We re all builders here, which usually means at some point we looked at something clunky, slow, or frustrating and thought, there has to be a better way. Most products don t start with a grand vision; they start with irritation, curiosity, or firsthand pain.

I d love to learn more about how others here have navigated that journey:

How did you uncover the problem you decided to work on?
What signals told you this problem was worth solving?
How did you validate (if at all) whether people would actually pay for a solution?
Has your product stayed true to the original problem, or did it evolve into something different?
What surprised you the most along the way?

The ultimate Chrome extension to automatically expand clipped Gmail messages. Stop clicking 'View entire message' forever. Zero data collection, privacy-first design.

https://www.producthunt.com/prod...

AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.

Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.

I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity.
It made me wonder ,what does your setup look like right now?

On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit

I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.