You Vibe-Coded an App. Nobody's Using It. Here's What Actually Works.

There is a specific kind of silence that follows shipping something you built in a weekend. The app works. The landing page looks good. You posted it once, somewhere, and got fourteen upvotes and one sign-up who never came back. Three weeks later the analytics dashboard is a flat line and you have started, quietly, building the next thing.

This is now the most common failure mode in indie software, and it is worth being precise about why.

Vibe coding solved the wrong bottleneck

Claude Code, Cursor, Lovable, v0 — whatever you're using — collapsed the cost of building. A SaaS that would have taken three months of evenings takes a long Saturday. That's a genuine step change and it's not going backwards.

But building was never the only bottleneck. It was just the one that felt like work. Distribution — the unglamorous business of getting the thing in front of people who need it — did not get cheaper. If anything it got harder, because everyone else's building also got cheaper, and the supply of decent-looking apps went up while the supply of attention stayed exactly where it was.

The uncomfortable version: your app being good is now table stakes, not an advantage. A lot of apps are good. Very few are known.

Why launches feel like they work and then don't

A launch is a spike. Product Hunt, a Show HN, a post to r/SideProject — these produce a burst of traffic on one day, and the burst decays with startling speed. This is not a criticism of launches; spikes are useful. They just aren't a channel, because a channel by definition keeps producing.

The mistake is treating the spike as validation of a distribution strategy. You got 400 visitors on launch day and 6 the following Tuesday. The 6 is your actual number. Everything you do from here has to move that one.

The channel nobody's saturating

Right now, today, people are posting things like this in public:

• "Is there a tool that does X without the enterprise pricing?"
• "What's everyone using for Y these days?"
• "Finally cancelled our Z subscription — what should we move to?"
• "Built a hacky script for this because nothing existed. Am I missing something obvious?"

Each of those is a person who has already decided they have the problem, has already decided to solve it, and is asking strangers for a recommendation. In paid-acquisition terms this is the bottom of the funnel — the part you normally pay the most to reach. It is sitting in public, for free, and almost nobody is systematically watching it.

The reason nobody's watching is that it's genuinely tedious. Reading six subreddits every morning to find one relevant thread is an hour a day for a hit rate that makes you quit in week two.

The rules that keep this from backfiring

Community replies work until you treat them like ad inventory, at which point they stop working permanently. A few rules that are not optional:

Answer the question that was asked. If someone asks how to solve a problem and your reply is a product pitch, you have not answered them and everyone reading can tell. Give a real answer first, one that would still be useful if your product didn't exist.

Disclose that you built it. "Full disclosure, I made this" costs you nothing and buys a surprising amount of goodwill. Reddit punishes stealth marketing far more harshly than honest self-promotion. The people who get banned are almost never the ones who said who they were.

Recommend competitors when they fit better. This feels insane and it is the single highest-return behaviour in this channel. Being the person who says "honestly for your use case, use X instead" makes your recommendation credible the next time, and people remember it.

Reply within hours, not days. Reddit threads decay fast. After about a day the OP has usually decided and your reply lands in an empty room. This timing constraint, more than anything else, is what makes manual monitoring fail.

Two or three replies a day, maximum. The temptation once you have a list of matching threads is to work through all of them. Don't. Volume is what gets accounts shadowbanned, and a rushed reply is worse than no reply.

Where to actually be

For most vibe-coded products the useful communities are narrower than you'd guess. r/SideProject and r/SaaS are obvious and correspondingly crowded. The better returns are usually in the specific subreddit for the problem you solve — r/webdev, r/smallbusiness, r/nocode, r/selfhosted, whichever one matches — where a thread gets three replies instead of thirty.

Hacker News deserves separate mention. "Ask HN: what are you using for X" threads are effectively buying-intent surveys you didn't have to run, and the audience skews toward people with budget authority. If your product has any technical angle at all, HN converts better per visitor than almost anything else organic.

The honest caveat

None of this rescues a product nobody wants. If you shipped fast and the underlying idea is weak, you will surface leads, reply to them, and convert none — and you'll conclude the channel doesn't work.

It's worth stating the more useful interpretation: in your first month, the threads themselves are worth more than the leads. The language people use to describe the problem, the alternatives they mention, the objections they raise — that's the market telling you what to build and how to describe it. Read them before you reply to them.

Making it sustainable

The reason this channel gets abandoned isn't that it doesn't work. It's that the monitoring is boring and you're a builder, so within two weeks you're back in the editor and the tab stays closed.

That's the specific problem Brew Me A Coffee exists to remove: scans run on a schedule across Reddit, Hacker News, and GitHub Discussions, each candidate gets scored for relevance, buying intent, and urgency, and what reaches you is a short list with a stated reason attached. You still write every reply yourself — that part shouldn't be automated and automating it is exactly what gets people banned.

There's a fuller version of this playbook on the page for vibe coders, including the specific communities and phrasings worth tracking.