The Indie Hacker's Guide to Hacker News Show HN

You spend months building something, you finally feel ready to show it, you post it to Show HN, and then you sit there refreshing the page while it gets four upvotes and slides off the new page in twenty minutes. That outcome is so common it should be the default expectation, and almost nobody warns you about it.

Show HN can still be one of the best places an indie developer can launch, because the audience is exactly the people who try new tools, file thoughtful bug reports, and tell their friends. The catch is that this same audience has a finely tuned allergy to marketing, and most launches fail not because the product is bad but because the post breaks unwritten rules the regulars enforce without mercy. Here is what actually moves a Show HN post, from someone who has watched a lot of them succeed and fail.

What is Show HN, and what does it actually reward?

Show HN is a category on Hacker News for sharing something you built that people can try right now: an app, a tool, a side project, an open-source release. You prefix the title with "Show HN: " and you link to the working thing. Y Combinator publishes official Show HN rules that are short and worth reading before you post, because breaking them is the fastest way to get flagged.

The thing to understand is what the audience rewards, which is a working thing over a promise. A landing page with a waitlist and three testimonials will do worse than a rough tool with a live demo and a couple of obvious bugs, because the first one asks the reader to trust you and the second one lets them judge for themselves. Hacker News is built for people who would rather click around for sixty seconds than read your value proposition. Give them something to click.

This shapes everything downstream. If your product cannot be tried without a credit card, an enterprise sales call, or a thirty-minute onboarding, Show HN is the wrong launch venue, or at least you need a free, instant way in before you post. Picking a launch channel that fits how your product is tried is one of the indie app marketing mistakes that quietly sinks otherwise good products. The lowest-friction path from the comment thread to using the thing is the single biggest predictor of whether a post goes anywhere.

When should you post a Show HN?

Timing is the thing people overthink the most, so let me put it in proportion: it matters, but less than the post itself. Hacker News traffic skews heavily toward United States working hours, and the new page moves fast, so posting when the most people are awake and browsing gives your post the largest pool of potential early voters while it is still fresh.

In practice that means a weekday morning in US time zones, roughly 7am to 10am Pacific, when both coasts are online and the day’s posts have not yet piled up. Avoid late Friday, Saturday, and Sunday, when traffic thins out and your post can drift off the new page before enough people see it. Those are not hard rules, just a way to stack the odds slightly in your favor.

The reason timing only matters at the margin is that the front page is decided by early momentum, not by the clock. A post needs a cluster of genuine upvotes in its first hour or two, when it is sitting on the new page where the most active users browse. The best time to post is the time that puts your fresh post in front of the largest number of those early browsers. After that, the post sinks or climbs on its own merits, and no posting time fixes a weak one.

How do you write a Show HN title that gets clicks?

The title is the highest-leverage thing you control, and it is where most launches quietly die. The format is fixed: "Show HN: " followed by a plain description of what the thing is and does. That second part is where you win or lose.

The rule is to describe, not to sell. The HN audience reads marketing language as a signal that the thing underneath is thin, so every hype word actively works against you with the exact people you are trying to reach. Compare these two:

• “Show HN: The revolutionary AI platform that supercharges your growth”
• “Show HN: A tool that turns your product URL into a growth plan”

The first one tells the reader nothing concrete and triggers their skepticism. The second one tells them exactly what it does in plain words, which is the only thing they actually want to know before they decide whether to click. Specific and modest beats grand and vague every single time on this platform.

A few concrete title rules that hold up:

• No exclamation marks. They read as desperate.
• No “revolutionary,” “game-changing,” “AI-powered,” or any adjective doing the work the product should do.
• Name the thing it does, not the outcome it promises. “Turns a URL into a growth plan” not “helps you grow faster.”
• If it is open source or free, that is worth saying plainly, because it lowers the friction to trying it.
• Keep it short enough to read in one glance.

Spend real time on this. I would rather write twenty title drafts than one extra feature, because the title is the entire pitch and you get one shot at it.

What can you learn from Show HN launches that actually worked?

The most documented launch in this format’s history is Dropbox. In 2007, Drew Houston posted a demo of Dropbox to Hacker News, and instead of a polished marketing page, he showed a screencast of the product working: files syncing across machines in real time. The famous part is the top comment, which dismissed the whole idea, suggesting you could replicate it yourself with existing tools like rsync and version control. Dropbox went on to become a multi-billion-dollar company. The lesson is not “ignore feedback.” It is that a clear demonstration of a real thing solving a real annoyance beats any amount of explanation, and that the loudest skeptic in your thread is not your market.

I want to be honest about the rest: precise upvote counts and dramatic origin stories get exaggerated constantly in launch retrospectives, so rather than feed you numbers I cannot verify, here are the repeatable patterns behind the launches that consistently do well. These hold up across years of watching the front page.

1. The scratch-your-own-itch tool. “I kept hitting this problem, so I built this.” The framing is honest, the motivation is obvious, and the audience recognizes the problem because they have it too. Authenticity is not a tactic here, it is the whole appeal.

2. The live, no-signup demo. Tools you can use immediately in the browser, with no account required, consistently outperform ones gated behind signup. Removing every step between the comment thread and the product is worth more than any feature.

3. The open-source release. Posting the repo, the architecture, and an honest README earns goodwill from a crowd that values being able to read the code. Even a commercial product with an open-source core gets a warmer reception.

4. The sharp, narrow tool. Something that does one specific thing extremely well, described in one specific sentence, beats a broad platform every time. The narrower the claim, the more credible it is.

5. The transparent founder. Posts where the maker is present in the comments, answering questions, admitting limitations, and saying “good catch, I’ll fix that,” turn a launch into a relationship. The thread becomes the launch.

Notice that none of these are about the product being finished or perfect. They are about being real, being specific, and being present.

How should you handle the comments?

The comments are not a side effect of the launch. They are the launch. A post with an active, thoughtful comment thread climbs, and a post with no comments dies quietly no matter how many upvotes it scrapes together, because comment activity feeds the ranking and signals to other readers that something is happening here.

The make-or-break moment is the first critical comment, and you will get one. Someone will tell you your idea is obvious, that a free tool already does this, that you have missed something fundamental, or that they could build it in a weekend. How you respond decides the tone of the entire thread. The rule that has never failed me: answer the substance, never the tone. If someone says “this is just X with extra steps,” resist the urge to defend your honor and instead explain, calmly and specifically, what is different and why you made that choice. Onlookers are reading your response far more than the original complaint, and a gracious, substantive reply does more for your launch than the criticism did against it.

A few more things that hold up in the comments:

• Be present for the first few hours. Replying within minutes while the thread is live matters more than a perfect reply hours later.
• Admit real limitations openly. “You’re right, it doesn’t handle that yet, it’s on the list” builds more trust than spin.
• Answer questions with specifics, not pitches. People asking how it works want a real answer, not a redirect to your homepage.
• Thank people for genuine bug reports and feedback. This crowd files some of the best you will ever get.

What happens if it flops?

Most Show HN posts do not hit the front page. That is the normal, expected outcome, not evidence that your product is bad or that you did something wrong. The new page is a firehose, the front page has limited slots, and a great deal of it comes down to who happened to be browsing in your first hour. Going in expecting a quiet launch will save you a lot of unnecessary discouragement.

Here is the reframe that matters: a launch that brings two hundred genuinely interested developers to your product, even if it never trended, is a good launch. Those are exactly the kind of early users who give real feedback and tell other people. The traffic spike from a front-page hit is nice, but most of it bounces. A smaller number of the right people is worth more than a flood of the wrong ones, which is the same principle behind getting your first 100 users the slow, durable way.

And it is not one shot. Hacker News allows reposting a project to Show HN when there is a significant update worth showing, so a quiet first launch followed by real improvement is a perfectly legitimate reason to share again. Read whatever comments you did get for product feedback, fix the things that were right, and treat the launch as one input among many rather than the verdict on your work.

That mindset, that a launch is a data point and not a referendum, is the same one I try to bring to all of indie marketing. A single channel rarely makes a product, and guessing which channel to pour your limited time into is where most solo founders waste months. That is the reason I built GrowthMap: you paste your product URL, and it pulls real data about your competitors, your audience, and the channels and communities where your people actually are, so your launch on Show HN or anywhere else is aimed instead of hopeful. You can run your own report for $19, and Show HN is exactly the kind of launch a real plan makes less terrifying.