Guide · 8 min read
Show HN App Launch: The Writeup Structure That Reaches the Front Page
Hacker News's Show HN tab is one of the few launch channels where having zero audience is not a structural disadvantage. Unlike Product Hunt — where upvote timing and network size decide your rank — Show HN rewards the quality of your post: the specificity of your title, the honesty of your first comment, and the genuine usefulness of what you built. In Q1 2026, only 2.3% of all HN submissions reached the front page. This is how the ones that did get there.
Show HN title format: the anatomy of posts that explain the thing in one line
The Show HN prefix does real algorithmic work: posts land in the dedicated /show tab, where downvotes are disabled for the first few hours. That grace period gives your post time to build upvote momentum before facing the full voting community. The prefix isn't cosmetic — it changes how HN's ranking system treats your submission. But the prefix alone does nothing without a title that earns a click.
The consistent format across front-page Show HN posts is "Show HN: [Product Name] – [what it does in the most specific terms possible]." The dash or em dash separates the brand name from the functional description. What goes after it determines everything. "Show HN: Datascribe – transcribe any audio file for free in your browser" tells you who it's for, what it does, and the key differentiators in eleven words. "Show HN: Datascribe – AI-powered audio transcription tool" tells you category and method but nothing memorable.
Specific constraints earn clicks: "without a server," "in your browser," "under 50ms," "no account required." These signal technical craft and attract the HN audience that respects craft. Avoid adjectives like "powerful," "beautiful," or "smart" — the HN community treats marketing adjectives as noise. The test: can a reader summarize what your app does from the title alone, without clicking? If not, your title is a description of a category, not a description of a thing.
The first comment structure that earns engagement from HN engineers
Your first comment, posted immediately after submitting, is the most important piece of writing in your Show HN. It's what organic visitors read before deciding whether to upvote or engage. Product descriptions written in marketing voice — "We built X to help teams do Y at scale" — reliably produce minimal engagement. Founder-voice writing that describes a specific problem and a genuine observation from building earns comments.
The structure that works consistently: one sentence describing the specific friction (not the category — the friction), two sentences explaining what you built and how it differs from existing solutions, one sentence about what you discovered during testing that surprised you, and a direct invitation for feedback on the part you're least certain about. Four sentences is plenty; six is the maximum before you've lost them. Anything that sounds like a product launch announcement rather than a person explaining something they made gets scrolled past.
What does not belong in the first comment: a feature list, a pricing table, a paragraph about the market opportunity, or anything that sounds like a pitch deck. HN readers detect pitch-deck language immediately and it signals low authenticity. The audience you're trying to impress is full of people who have built things themselves. They respond to peer-to-peer honesty — a limitation you chose, a trade-off you made, a detail you got wrong on the first try — far more reliably than to polished promotional copy.
What the HN audience upvotes: craft signals that separate front page from /newest
Front-page Show HN posts for apps cluster around a recognizable set of characteristics. The most reliable predictor is whether the app does one thing sharply — a markdown editor that renders with unusual fidelity, a budgeting tool that requires zero categories, a screenshot tool that outputs every App Store format in one export. HN's upvote culture rewards solving one problem with unusual precision more than solving ten problems adequately. Breadth reads as unfocused; depth reads as craftsmanship.
The second predictor is technical honesty in the writeup. A first comment that mentions one trade-off you consciously chose ("we built offline-first, which means sync is manual for now") earns more engagement than one that only lists features. HN readers find acknowledged limitations reassuring — they signal the builder understands their own product. A fully polished pitch with no rough edges comes across as either oversimplified or evasive.
Apps that consistently underperform on Show HN: social apps that require onboarding before you can see the core value, tools that duplicate an existing app with only cosmetic differences, and anything where the primary revenue model is dark patterns. HN's core audience are engineers who immediately recognize these signals. What converts the same audience: tools they would genuinely add to their own workflow, open-source projects they could fork, and apps that solve a problem they can personally verify exists. If you wouldn't use it yourself, the post will reflect that.
Show HN timing: the posting window that gives your submission the longest runway
Hacker News has a distinct daily traffic pattern. The highest-engagement window for new submissions is US East Coast morning — roughly 9 AM to 12 PM ET — when the East Coast professional audience is at their desks and the West Coast audience is arriving. Posts in this window have more active voters during their critical early growth period. Most experienced HN launchers target 9–10 AM ET on Tuesday, Wednesday, or Thursday for Show HN submissions. Wednesday is the peak for consumer and mobile apps specifically.
Weekend timing is more nuanced. Saturday has a smaller but more engaged audience, often producing higher-quality comments from people who have time to actually try the thing. Sunday is the lowest-traffic day and not recommended for a high-stakes launch. Monday morning carries extra variance — posts from the weekend are still collecting late votes, compressing attention for new submissions. The first 30–60 minutes after posting are the most critical window: posts that reach 30–50 upvotes within the first hour have a meaningful shot at the front page.
One underused approach: a second submission after a first attempt fails to gain traction. HN permits resubmitting the same product after enough time has passed, and many successful Show HN posts were not the first submission of that product. Timing, title phrasing, and whether competing content dominated that day all affect outcome independently of the product's quality. A "failed" Show HN is frequently a timing or framing problem, not a product problem. If the first attempt stalls, wait three to four weeks, revise the title based on what you learned, and try again.
Converting HN traffic to App Store installs before the 24-hour spike ends
A front-page Show HN routes traffic to your homepage, not your App Store listing directly. HN visitors are skeptical and fast-reading; they will not tap a large "Download on App Store" button before they understand what the app does. The homepage pattern that converts HN traffic: a one-line statement of the specific problem above the fold, two to three sentences explaining how you solve it differently, and a screenshot or demo GIF showing the app actually working. The App Store button should be secondary to evidence of a working product.
Your App Store listing is where HN visitors who do convert continue their decision process. Screenshots that read at thumbnail size, a subtitle that mirrors the clarity of your Show HN title, and a first screenshot that shows an outcome rather than the home screen all reduce the drop-off between "clicked App Store link" and "installed." Fix these before you post — HN traffic is fast and single-use. You don't get a second Show HN spike with the same product on the same timeframe. The AppsTemple editor builds screenshots at the exact pixel dimensions Apple and Google require; the template library includes outcome-first layouts designed for this conversion context.
Reply to every comment in the first two hours after submission. Engagement velocity — upvotes plus comments plus maker replies — is one of the signals HN's algorithm uses to surface posts in the feed. A launch with 40 upvotes and 15 active comments frequently outranks one with 60 upvotes and 2 comments. Keep your replies specific to what each commenter said; a genuine two-sentence reply to a technical question contributes more signal than a generic acknowledgment. The half-life of HN front-page traffic is about 24 hours — the optimization work happens in real time, not after the fact.
Five patterns that get a Show HN post buried before it finds its audience
Marketing voice in the title. "Revolutionize your workflow" or "the next-generation X" signals promotional intent immediately. HN readers flag posts that read like press releases. Be specific, functional, and plain. If you find yourself using an adjective that doesn't add information — powerful, beautiful, seamless — delete it. Requiring sign-up to see value. HN readers will not create an account to evaluate your app. If the core experience requires onboarding, mention it and explain what visitors will see, or link to a demo that skips it. The barrier has to drop or the evaluation doesn't happen.
Responding defensively to criticism. HN comments include harsh, accurate feedback from experienced engineers. Responding with "that's not a problem our users have mentioned" or explaining away a valid technical concern will damage your post faster than the original criticism did. Acknowledge what's real. The founders who earn the most goodwill on HN are the ones who say "you're right, here's the trade-off we made." Vote manipulation. HN's anti-abuse system detects coordinated upvote patterns — votes from accounts created around the same time, votes clustered immediately after submission, votes from the same IP range. Getting caught triggers silent penalization: your post shows your vote count but stops surfacing in the ranking feed. It looks like you're on HN. You aren't.
Submitting before the product works end-to-end. The Show HN guidelines are explicit: it is for something you have built, not something you plan to build. A landing page with a waitlist form inverts the relationship — you're asking visitors to invest in you before demonstrating value to them. If your app crashes on the first core action, or requires environment setup to run, post a build that works for someone who has never touched it before. The HN audience is generous with first-time builders who ship something real; it is merciless with anything that reads as premature. See the 6-week launch checklist for the preparation sequence that gets you to a submittable state.
Prepare your App Store listing before you submit — HN traffic won't wait
The window between posting your Show HN and the first wave of organic visitors finding it is measured in minutes, not hours. Any conversion work that happens after the spike has already missed most of the traffic.
The assets that matter most for converting HN visitors to installs are your first App Store screenshot (the one that appears in search results before users tap to expand) and your subtitle. Both need to communicate the same specificity as your Show HN title. AppsTemple's editor lets you build at exact App Store and Play Store dimensions with device frames in place — iterate and export before you post.
Build your App Store screenshots before launch →
Frequently asked questions
what is show hn and how is it different from a regular hacker news post?
Show HN is a special submission prefix on Hacker News for sharing something you've built. Posts using "Show HN:" appear in the dedicated /show tab, receive downvote protection for the first few hours, and get a grace period to build momentum before facing the full voting community. A regular HN submission receives no such protection. Show HN is intended for completed products, tools, or experiments — not ideas, plans, or landing pages.
what is the best time to post a show hn?
The highest-engagement window is 9–10 AM ET on a Tuesday, Wednesday, or Thursday. This places your post when the East Coast professional audience is at their desks and the West Coast is arriving. Wednesday is the peak for consumer and mobile apps. Avoid Monday (lower engagement coming off the weekend) and Friday (audience disengages before the window closes). The first 30–60 minutes after posting are the most critical for building upvote momentum.
how many upvotes does a show hn need to reach the front page?
There is no fixed threshold — HN's ranking algorithm weights upvote velocity (how fast votes arrive), account credibility of voters, engagement (comments plus maker replies), and time decay. In practice, posts that reach 30–50 upvotes within the first hour have a meaningful shot at the front page. Posts that reach only 10–15 upvotes in the first hour rarely recover their rank regardless of what happens later. Engagement quality matters as much as raw upvote count.
can i resubmit my app to show hn if the first post failed?
Yes. HN permits resubmitting a product after sufficient time has passed, and many successful Show HN posts were not their first submission. A failed first attempt is often a timing or title problem rather than a product problem. Wait at least three to four weeks, revise the title based on what you learned about how visitors described or dismissed it, and resubmit during the optimal posting window. Do not resubmit within a few weeks — HN's system recognizes recent duplicate content.
how do i write a good show hn first comment?
One sentence describing the specific problem you solve (not the category — the actual friction), two sentences explaining what you built and how it differs from alternatives, one sentence about something you discovered during testing that surprised you, and a direct question asking for feedback on the part you're least certain about. Four sentences is the target; six is the maximum. Avoid marketing language, feature lists, and pricing. Write as if explaining to a fellow developer what you made and why — because that's exactly who will read it.