Back to Details

launch-it

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Launch it

发布产品

Developer communities reward the honest, technical, slightly humble builder and punish the marketer instantly. A Show HN is not an announcement. It's "I built this thing, here's how it works and what's still rough."
Use this when: you're scared to launch, you're hoping to "go viral," or you're about to drop marketing copy into a room that eats marketing copy for breakfast.
开发者社区青睐诚实、懂技术、略带谦逊的创作者，会立刻抨击营销人员。Show HN不是公告，而是“我做了这个东西，这是它的工作原理，还有哪些地方不够完善”。
适用场景： 你不敢发布产品、希望产品“病毒式传播”，或是打算向一个以“消化营销文案为乐”的社区投放营销内容时。

The core idea

核心理念

The bar is usefulness + honesty, not polish. Developers will test your claims and read your code. Show up as a real engineer sharing real work, be present to answer everything, and never, ever fake it. One genuine launch beats ten hype posts.
关键在于实用性+诚实，而非完美度。开发者会验证你的说法、阅读你的代码。以真实工程师的身份分享真实成果，全程在场解答所有问题，绝对不要弄虚作假。一次真诚的发布胜过十篇炒作帖。

Framework: Show HN anatomy (Czakon / Tailscale lessons)

框架：Show HN发布结构（Czakon / Tailscale经验总结）

  1. Title: plain, specific, zero hype. "Show HN: A faster Postgres migration tool for large tables", not "🚀 The future of database migrations is HERE."
  2. First comment = the story (post it yourself, immediately):
    • why you built it (the itch, ideally your own),
    • how it works (technical, concrete),
    • what's genuinely hard/limited right now (honesty buys trust),
    • a dead-simple way to try it.
  3. Be present for hours. Answer every comment, especially the critical ones, technically and without defensiveness. The comment thread is the launch.
  4. Never astroturf. No vote rings, no sock puppets. Communities detect it and the ban is permanent and public.
  1. 标题：直白、具体、零炒作。 比如“Show HN：针对大表的更快Postgres迁移工具”，而非“🚀 数据库迁移的未来已到来”。
  2. 第一条评论 = 故事（自行立即发布）：
    • 你开发它的原因（最好是解决自己的痛点），
    • 它的工作原理（技术层面、具体细节），
    • 当前真正的难点/局限性（诚实换取信任），
    • 一种极其简单的试用方式。
  3. 全程在场数小时。 回复每一条评论，尤其是批评性的评论，用技术角度回应且不带防御性。评论区就是发布的核心。
  4. 绝对不要刷量造假。 不要搞投票团伙、不要用小号。社区能识破这种行为，且会永久公开封禁你。

Framework: Product Hunt anatomy (fmerian / Kilo lessons)

框架：Product Hunt发布结构（fmerian / Kilo经验总结）

  1. Name of the product: simply the name of your product in 40 characters or less.
  2. Tagline: concise and descriptive, in less than 60 characters. The most important part, the first thing people read on the front page. Avoid hyperbolic words and emojis. Keep it simple and relatable.
  3. Description: a short description of what the product does in less than 500 characters.
  4. Launch tags: up to three tags.
  5. Thumbnail: a 240 x 240 pixel thumbnail.
  6. Image gallery: at least 3 images to show your product. No stock images, no marketing fluff. Show the product, i.e. product screenshots. You can add social proof and a call-to-action to inspire action. The first image is used as the social preview when you share the link to your launch page.
  7. First comment: essential to get the discussion started. This comment is posted upon launch. The first 800 characters are displayed. Pro tip: reuse your HN comment.
  8. Be present for the first 4 hours. Upvote and reply to every comment. Don't just thank. Ask questions, inspire action.
  9. Find a hunter: an established Product Hunt user who can boost your reach. If you're in dev tools, Flo Merian (@fmerian) is a great one to ask. PH has dialed down hunter influence over time, so a strong launch and a present founder matter most, but a well-connected hunter still helps.
Framework adapted from Flo Merian's awesome-product-hunt.
  1. 产品名称：仅用产品本名，不超过40个字符。
  2. 标语：简洁描述，不超过60个字符。 这是最重要的部分，是用户在首页看到的第一内容。避免夸张词汇和表情符号，保持简洁、贴近用户。
  3. 描述：简短说明产品功能，不超过500个字符。
  4. 发布标签：最多3个标签。
  5. 缩略图：240×240像素的缩略图。
  6. 图片库：至少3张展示产品的图片。 不要用库存图片、不要有营销废话。展示产品本身，比如产品截图。你可以添加社交证明和行动号召来激发用户行动。第一张图片会作为你分享发布页面链接时的社交预览图。
  7. 第一条评论：开启讨论的关键。 这条评论在发布时同步发出，前800个字符会被展示。小贴士：复用你在HN上的评论内容。
  8. 发布后前4小时全程在场。 为每条评论点赞并回复。不要只说谢谢，要提问、激发用户行动。
  9. 寻找猎人：一位资深Product Hunt用户，可提升你的曝光度。 如果你做的是开发者工具，Flo Merian (@fmerian) 是个不错的人选。虽然Product Hunt已逐渐降低猎人的影响力，但一场出色的发布和创始人的全程参与仍是关键，不过人脉广的猎人仍能提供帮助。
本框架改编自Flo Merian的awesome-product-hunt。

Reddit / community launches

Reddit / 其他社区发布

  • Give before you take. Be a real participant for weeks before you post your thing.
  • Read the rules of the specific subreddit; many ban self-promo outright, so find the ones that don't.
  • Frame as "I made this to solve X, feedback welcome," not a pitch.
  • 先予后取。 在发布你的产品前，先作为真实用户参与社区活动数周。
  • 阅读具体子版块的规则：许多子版块完全禁止自我推广，所以要找到允许的版块。
  • 以“我做这个是为了解决X问题，欢迎反馈”的口吻发布，而非推销。

The coordinated moment (not spam)

协同发布时刻（而非垃圾推送）

A launch is one prepared moment across the channels your ICP actually uses (from 
first-50-users
): HN, your own network, and the relevant communities, all on the same day, each tailored to the room. It is not the same copy blasted five places.
发布是一个精心准备的时刻，在你的ICP（理想客户画像）实际使用的渠道（参考
first-50-users
）同步进行：HN、你自己的人脉圈、相关社区，所有渠道在同一天发布，且内容要适配每个社区的风格。绝对不能把相同文案批量发到五个地方。

Decision tree: are you ready to launch?

决策树：你准备好发布了吗？

Can a stranger get to first value in < 1 hour from docs alone (the weekend test)?
├─ NO  → don't launch yet. A flood of users who bounce burns the channel and the goodwill.
└─ YES → is your Show HN first-comment written (why/how/limits/try)?
         ├─ NO → write it first; it matters more than the product page.
         └─ YES → launch on a Tue-Thu morning US time, then clear your calendar to reply.
陌生人仅通过文档就能在1小时内获得首次价值吗（周末测试）？
├─ 否 → 暂不发布。大量用户涌入后流失会损害渠道声誉和你的好感度。
└─ 是 → 你的Show HN第一条评论写好了吗（原因/原理/局限性/试用方式）？
         ├─ 否 → 先写评论；它比产品页面更重要。
         └─ 是 → 在美国时间周二至周四上午发布，然后清空日程回复评论。

Mistakes that look reasonable

看似合理的错误

  • Hype title: emojis and superlatives on HN get flagged to death.
  • Absent founder: posting then leaving; the unanswered thread dies.
  • Defensive replies: arguing with critics. Thank them, concede the fair points, note what you'll fix.
  • Astroturfing: instant, permanent reputational damage.
  • Launching too early: before the weekend test passes, a launch amplifies your weakest moment.
  • 炒作标题：HN上的表情符号和最高级词汇会被疯狂标记。
  • 创始人缺席：发布后就消失；无人回复的评论区会很快沉寂。
  • 防御性回复：与批评者争论。要感谢他们，承认合理的观点，记录你会修复的问题。
  • 刷量造假：瞬间造成永久的声誉损害。
  • 发布过早：在通过周末测试前发布，会放大你产品最薄弱的环节。

Your next 30 minutes

你接下来30分钟的任务

  • Draft your Show HN title, plain, specific, no hype. Say it out loud; if it sounds like an ad, redo it.
  • Write the first comment: why · how · what's hard · how to try. This is the real work.
  • Confirm the weekend test passes (see 
    know-if-its-working
    ). If not, delay.
  • Pick the ONE day, block 4 hours to reply, and line up the 2-3 rooms your ICP is actually in.
Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). When a framework can't make the call, that's what a human is for: The DevTool GTM Company.
  • 草拟你的Show HN 标题，直白、具体、无炒作。读出来听听；如果听起来像广告，就重写。
  • 撰写第一条评论：原因·原理·难点·试用方式。这才是核心工作。
  • 确认通过周末测试（参考
    know-if-its-working
    ）。如果没通过，推迟发布。
  • 选定唯一的发布日期，预留4小时回复评论，并确定2-3个你的ICP实际活跃的社区。
基于真实的开发者工具GTM（上市策略）经验构建，框架来自Adam Frankl（《面向开发者的创业公司》）和Jakub Czakon（markepear.dev）。 当框架无法做决策时，就需要人工介入：The DevTool GTM Company。