From Beta Lists to Weekly Archives: Launch Lists Explained
Background · 8 min read ·
A short history of how startups have announced products, from email lists and forums to leaderboards and permanent directories, and what it means today.
New products have always needed somewhere to be announced. Before the web, a shop opening got a notice in the local paper and a product launch got a trade magazine column. Online, the same need produced a succession of formats, each solving something its predecessor did badly. Knowing the lineage helps you choose where to spend your time today, because each format still carries traces of the problem it was built to solve.
This is a short, practical history. It does not claim to be complete, and it sticks to what can be checked.
Stage one: the forum thread
The earliest launch announcements online were posts in forums and mailing lists. A developer would write "I built this, tell me what you think", and readers would reply. The strength of the format was honesty: people who liked your work said so, and people who did not explained why.
Its weakness was findability. A thread belongs to its day. Search can sometimes surface it later, but the format has no structure for browsing by category, and a good launch could vanish beneath the next hundred posts.
Hacker News is the best-known descendant. Wikipedia records that it was launched on 19 February 2007 by Paul Graham, originally under the name Startup News, and describes it as a social news site focused on computer science and entrepreneurship, run by Y Combinator. Its Show HN convention gives makers a defined way to share their own projects, and its guidelines are strict about what qualifies: something people can try, not a sign-up page, a newsletter or a landing page.
Stage two: the beta list
As more people built products, a need appeared for a place that gathered early-stage work in one spot, so that a person curious about new things did not have to scour forums. Beta lists answered it. They collected newly submitted startups, sorted them by category and sent a regular digest.
BetaList still describes itself in these terms: a way to find early-stage startups before they make it big, with browsing by category and a daily email of the newest ones. The format's strength is curation. Its weakness is scale, since any list that depends on a human reviewing submissions has to choose what to feature.
Stage three: the community leaderboard
The next step was to let the audience decide. Rather than an editor choosing what mattered, readers would vote, and a ranking would emerge. Product Hunt is the best-known example. Wikipedia says it was established by Ryan Hoover in November 2013, started life as an email list, and became a website that first holiday season. It later attracted investment and was acquired by AngelList in 2016.
Its present form, in its own words, is a homepage leaderboard based on community engagement, where products can earn titles such as Product of the Day, and it is free to use.
The leaderboard solved the curation bottleneck and created a new dynamic. Attention concentrated on a short window, which rewarded preparation and community. It also produced a new craft: the launch day, with its scheduling, its first comment and its etiquette. Product Hunt's guidance notes that direct requests for upvotes violate its guidelines and that engagement through comments matters.
Stage four: the community hub
Alongside launch sites, communities grew around the broader business of building something. Indie Hackers describes itself as a place where people work together to build profitable online businesses, with discussion posts, a database of case studies and products, and a newsletter. A launch there is less a contest than a conversation embedded in a continuing story.
The hub model matters for launches because it shows that attention is not only about the day. Founders who share progress regularly build an audience that is ready when a product ships.
Stage five: the archive
The most recent format returns to something older than all of the above: the catalogue. An archive keeps every launch on its own page, organised and linkable, and treats the long tail as the point rather than a side effect.
The format has an obvious ancestor in directories and indexes, but it benefits from modern tools: sitemaps, structured data, consistent categories and the practice of qualifying links honestly. Google's SEO starter guide notes that most of the new pages it discovers come through links, which is exactly why a well-linked archive can keep working long after publication.
What each stage got right
Reading the lineage as a story of progress would be a mistake. Each stage kept something the next one tended to lose.
- The forum kept honesty and conversation.
- The beta list kept curation and a sense of taste.
- The leaderboard kept energy and the power of a crowd.
- The hub kept continuity and relationships.
- The archive kept lasting pages and findability.
A founder who wants the best outcome uses each for what it does best. A forum post for candid feedback. A list for curated discovery. A leaderboard for a burst of attention. A hub for steady relationships. An archive for the long record.
What stayed constant
Despite the changes in format, the things that make a launch work have barely moved.
A clear description. Every format rewards a product that can be explained in a sentence.
Something to try. People want to see it work. Hacker News's guidance on removing barriers to trying a project echoes through every platform.
Honest engagement. Replying to people, thanking them and acting on their comments matters in all formats.
Consistency. Founders who show up repeatedly, with updates and improvements, are remembered.
Respect for the audience. Every platform that has lasted has set rules against manipulation, because manipulation spoils the thing people came for.
What changes for you
For a founder in the present day the lesson is to stop asking "which platform is best?" and ask "which job is this for?" If the job is feedback, go where conversation lives. If it is early users, go where people who like trying new things gather. If it is a durable record, choose an archive and write the entry as if it will be read for years.
It also means being wary of nostalgia and novelty alike. A format that was ideal a few years ago may have changed its rules or its audience, and a shiny new platform may not last. Check any claim about audience size or traffic yourself, and treat marketing copy as copy.
Looking after your own history
Whichever formats you use, keep your own record. Save screenshots of your listings, note the dates, and keep the text you submitted. Over time this becomes your launch history: useful for your own planning, and useful for anyone writing about you. The article on keeping a listing current after launch gives a short routine.
Why each format keeps getting reinvented
If these formats each solve something, why does a new one keep appearing? Three forces keep pushing the cycle round.
The first is saturation. When a platform becomes popular, more founders compete for the same attention, and early advantages such as novelty fade. People begin to look for places where their product will not be one of hundreds on the same morning.
The second is specialisation. A general site cannot serve every audience equally. A developer tool, a local bakery and a fashion label have different buyers, different vocabularies and different ideas of what a good listing looks like. Newer platforms often focus on a niche for this reason.
The third is trust. Any ranking system invites attempts to game it, and the platforms that last put real work into fairness. Product Hunt's own guidance says direct upvote requests violate its rules, and Hacker News tells posters not to ask others to upvote or comment. When a format loses trust, people move on to one that has it.
For the founder this is mostly good news. It means there are more places to be seen than ever, and more honest competition among platforms to treat you well. It also means you should expect to revisit your choices every year or two rather than settle on one for life.
A reading list for the curious
If you would like to understand the formats first-hand, spend an hour doing the following. Read the Show HN guidelines in full and then look at five recent examples to see which follow them. Browse a beta list by category and ask what the editors seem to value. Open a leaderboard and read the comments, not just the ranks. Find a community hub and read two founder case studies from start to finish. Finally, open an archive and look at an entry from a year ago. Notice how well each aged. That hour will teach you more about what works than any number of opinion pieces, including this one.
Where we fit
We are an archive in the sense described above. Every launch has its own page, organised by category and week, with its facts kept in one place. If you decide to list, the submit page begins the process, and the about-founders page says who built it. A launch listing currently costs $5, and our live Ahrefs DR is 0 for anyone who wants to compare.
The history of launch lists is a history of people trying to answer the same plain question: where do I tell the world about the thing I made, and how do I make sure someone is listening? The answers have changed. The question has not.
Questions and answers
- When did Product Hunt start?
- According to Wikipedia, Product Hunt was established by Ryan Hoover in November 2013 and began as an email list before becoming a website.
- What is Show HN?
- Show HN is a convention on Hacker News for sharing something you have made that others can try. Hacker News was launched by Paul Graham on 19 February 2007, initially under the name Startup News.
- Why have so many launch platforms appeared?
- Founders need audiences and audiences need discovery. Each generation of platform has tried a different balance between community voting, editorial curation and permanent cataloguing.
- Which kind of platform lasts longest?
- Format matters less than usefulness. Platforms that keep their entries accurate and their audience engaged tend to last, whatever their structure.