# HN public API launch tracker before vanity summary

> Build a small launch tracker from public HN and GitHub data before reducing the launch to one screenshot of the front page.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/hn-public-api-launch-tracker-before-vanity-summary/
- Source: [arxiv.org](https://arxiv.org/abs/2511.04453)
- GrowthDex source hub: [arXiv: Launch-Day Diffusion: Tracking Hacker News Impact on GitHub Stars for AI Tools](/sources/arxiv-launch-day-diffusion-tracking-hacker-news-impact-on-github-stars-f/)
- Last checked: 2026-06-10T06:39:08.000Z
- Rarity: rare
- Budget: free
- Channels: Hacker News, Analytics, GitHub
- Stages: public APIs, launch tracker, GitHub analytics, HN comments, post-launch learning


## Why this can grow

A launch screenshot is a memory. A launch tracker is an operating tool. The diffusion paper's demonstration used public APIs, completed in under five minutes on standard hardware, and collected data, trained models, and generated visualizations through single-file scripts. A founder does not need the full research pipeline. A small version is enough: timestamp the post, record comments and score, pull GitHub stars, forks, contributors, issues, clones if available, docs clicks, and repo traffic, then compare the 24-hour, 48-hour, and 7-day windows. That turns HN from folklore into a source of reusable launch learning.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where hn public api launch tracker before vanity summary can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and Analytics channel.
3. Use the evidence from arxiv.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

The Launch-Day Diffusion demonstration is built on public APIs and completes in under five minutes on standard hardware while collecting data and generating visualizations.

## Adjacent tactics in the same lane

- [HN star-window ledger before launch retrospective](/growth-ideas/hn-star-window-ledger-before-launch-retrospective/) - same source, 2 shared channels
- [HN posting-hour test before front-page hope](/growth-ideas/hn-posting-hour-test-before-front-page-hope/) - same source, 1 shared channel
- [HN Show label after substance, not before](/growth-ideas/hn-show-label-after-substance-not-before/) - same source, 1 shared channel
- [GitHub Discussions weekly review of views and contributors](/growth-ideas/github-discussions-weekly-review-of-views-and-contributors/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) - Hacker News, GitHub, developer marketing

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.