Connect with the Product Hunt community

how do you actually check if your idea's been done before? like - gpt it, google it, ask friends, dig through YC's directory, or just.. cross fingers and build?

asking because i built ExploreYC trying to fix exactly that... through semantic search on over 8.6k startups, but genuinely curious what people reach for before a tool. what's your move?

"Talk to users" is probably one of the most repeated pieces of startup advice.

And for good reason.

When it comes to AI Memory, everyone's arguing "RAG vs. grep" like it's a religious war. It's not. It's just a cost curve. I've gotten this question so many times that I thought I'd just share my thoughts. So here goes:
Vector search wins when your corpus is massive, messy, and unstructured. Thousands of docs, no clean boundaries, meaning matters more than exact words.
Filesystem plus grep wins when your corpus is structured and actually yours. A folder of markdown files you can open, read, and audit line by line. No infra required.
Anthropic already ran this experiment in production. Claude Code dropped its RAG pipeline for plain agentic search (grep, glob, read) and it outperformed the vector pipeline on real work. Not close.
But the benchmark wars are missing the actual point. It was never about picking one. It's about knowing what each layer is for.
Markdown is your source of truth. Portable, human readable, greppable, not locked to one provider. Memory you can actually own and move.
Vector search is an accelerant on top of that truth. A fast index for when the haystack gets too big for exact match to keep up.
Use either one alone and it breaks down:
- Markdown alone stalls at scale and struggles with paraphrasing or fuzzy recall
- Vectors alone turn your memory into a black box you can't read, audit, or export
The next step for memory infrastructure isn't picking a side. It's the filesystem as the ledger and RAG as the index on top of it, so memory stays legible and portable, and still fast when it needs to be.
This is the exact direction we're building with AI Context Flow: markdown as the portable, ownable source of truth, with retrieval layered on top instead of replacing it.
If your memory only exists as embeddings inside someone else's vector DB, that's not memory. That's a lease.
Which team are you on?

New products and better ways to work show up every week.

99% of new tools I found out on Product Hunt. I get around 95% of my AI news and ideas from Twitter.

The other 5% comes from YouTube tutorials.

Hey everyone,

We won Product of the Day. thank you so much to everyone who supported, upvoted, commented, tested Goldfish, and gave us feedback

Developers weren't meant to share secrets through email, Slack, or cloud storage.

Yet we've all emailed ourselves a .env file, pasted API keys into chat, or uploaded sensitive files to services that keep copies indefinitely.

We built BurnLink CLI to provide a better way.

Hey Product Hunt,

Breva 2.0 is finally live on iPhone!

I built Breva because I wanted a calmer way to reset during the workday without opening a full meditation app or getting pulled into my phone.

From what I am seeing across communities, here is what the tool stack looks like right now.

The Core Stack

Email & Capture: Mailchimp for launch updates and email sequences . Carrd for quick, clean launch-specific landing pages . Pre-launch tools like LaunchBuddy and Prefundia to build a waitlist and gather early feedback before you even hit the Product Hunt button .

Social & Scheduling: Buffer or Hootsuite to keep a consistent presence across X, LinkedIn, and Threads without it taking over your entire day . Canva for generating graphics that do not look like you threw them together in five minutes .

I know each of you probably has a rich list of online creators and publications that provide you with interesting ideas and useful tips. So I thought it would be a good opportunity to exchange recommendations.

For me, these are:

• Ad Professor

• Tom s Marketing Ideas

• PH Newsletter

Feel free to share your own list as well.

Where does your team keep project materials today?
Google Drive? Dropbox? Notion? Somewhere else?
We noticed something interesting while working on creative productions: finding a file is usually not the hardest part.
The hard part is remembering:
- Why was this version created?
- What feedback led to these changes?
- Which direction did the team agree on?
- Is this still the latest approved version?
A folder can store thousands of files, but it doesn t always store the story behind them.
That s something we ve been thinking about while building RunEvr s Materials module.
We wanted materials to stay connected to the workflow so context moves with the work.
Curious - how does your team handle this today?
Do you feel like you re losing context around your files?

The funny thing is that recording content isn't usually the hard part. Most people can talk for a few minutes, record a meeting, or capture an idea as soon as it comes to mind. The part that often stops people isn't creating. It's knowing they'll have to spend hours editing a few minutes of content.

We felt exactly the same while building @ProdShort

At first, we thought our biggest challenge was finding ideas for content. But over time, we realized that editing was the real pain...

What's the biggest thing stopping you from posting consistently?

The one where the AI chat stops living inside a panel and becomes an actual window you can put wherever you like. Also the one where we deleted a setting instead of adding one.

New

• Pop a chat out into its own window hit Ctrl+K in any AI chat (ask, palette, or the folder digest) and it flies off into a frameless window of its own. Drag it to the second monitor, keep reading mail underneath, and it keeps streaming the whole time.

• Close it and it comes home Esc, , Alt+F4, whatever you press, the conversation slides back inline exactly where it was. No "session expired", no starting over.

• Click a citation in a popped-out chat and the actual email opens in the main window which politely un-minimizes itself from the tray instead of making you go find it.

• Open a second, third, fourth chat window they cascade instead of stacking pixel-perfectly on top of each other, which was funny exactly once.

Half the threads here are about accuracy and fewer iterations. One source of rework I rarely see named: when I paste a screenshot, Cursor has to guess which element on a busy screen I actually meant, and it edits the wrong one. Then I'm re-prompting, which is its own iteration tax.

Curious how much of your rework is this specific thing versus raw model quality. And what's your fix, crop hard, or describe the element in text?

Small update for the people who ve been following Flowdy

A while back, I posted here looking for people to help shape Flowdy and some of you actually did. This is where that feedback led.

The honest problem with V1 was simple: it only helped merchants who already had content. Flowdy could turn blog posts and product descriptions into shoppable text, but if a store wasn t writing blog articles in the first place, there wasn t much to work with. And for a lot of stores, that s just the reality.

Six months ago we added a pause to Murror.

After you finish a journal entry, the AI waits. No instant analysis. No immediate insight. Just a small animation and 8 seconds of silence.

This is a question that does not get asked enough.

Right now, if you use a hosted AI memory tool, your context, your decisions, your preferences, your project history, all of it lives on someone else's servers. Governed by their retention policies. Subject to their pricing changes. Potentially readable by their team.

Hi everyone!

We re starting to test a new AI Co-host feature for Live Studio.

Hey dear Community !

While building RunEvr, we created different modules for creative teams - Materials, Tasks, Boards, Forums, Reviews, and more.

One part we re especially curious about is team communication

Our Forum module is designed around project-based conversations, and naturally users often compare it with Slack.

A few days ago Tamamon launched here and you made it #3 Product of the Day. Thank you genuinely. It's a tiny pixel pet that lives on your desktop and grows as you code with Claude Code, and since launch it's had ~30 updates almost every one straight from a comment in this thread. Here's what's new, and who it came from.

Every quarter, I set goals and then review how I did.

I started doing this two years ago after realising that New Year's resolutions simply don't work for me. To be fair, I don't always hit my quarterly goals either, but my success rate is much higher.

Today, we are launching on Product Hunt for the second time!

Since our first launch, we rebranded Denovo and improved the product with better customer acquisition agents.

Some of our founders have already started generating revenue!

Hey builders

Token bills are creeping up as we ship more AI features, and I'm curious how the community is dealing with it.

A few things I'd love your take on:

Hey everyone

Just shipped Netfox 0.14.0, and this one started with a bug report I couldn't stop thinking about.

I turned on my Apple TV and it wasn't in the list. Except it was sitting there as a phone, with no manufacturer, under the name I'd given it years ago.

I checked Google Search Console for my site. I wanted to know which of my twelve guide pages were bringing people in. None of them were.

The site got 87 clicks in 90 days. My brand name by itself was 56% of them. Most of the rest were people spelling my brand name wrong. Searches that had nothing to do with my name showed up three times in total.

So no new people are finding the site. Everyone who arrives already knew the name before they searched. I had been looking at those clicks and calling it growth. It was not.

I decided the fix was longer and more useful guides. Each one was about 450 words. They are now about 1,000. This time I checked real keyword data first, instead of guessing what people search for.

Most AI tools, when they're unsure, guess confidently.

That's how you burn an hour chasing the wrong bug.

We went the other way. Point ours at your repo and say what's breaking "customers are getting charged twice." Instead of guessing which API, it reads your code:

• Sees you have both Stripe and Paddle installed.

• Reads both webhook handlers your Paddle one has no idempotency check (line 16); Stripe dedupes fine.

• Tells you: "it's your Paddle handler." A fact from your code, not a hunch.