Science of Apps - Launchpad · Launch guide

How to launch
an open source project

Launch an open source project once someone can install it and get a result in minutes: a clear README with what it does, a quick start and a licence. Then post a Show HN linking to the repo, list it on DevHunt (open-source projects are accepted), launch on Product Hunt, and add it to AlternativeTo as open source. GitHub's Open Source Guides cover finding users.

By , FounderUpdated 4 min read

Share

Quick answer: How do I launch an open source project?

  1. Ready when: install to first result in minutes.
  2. README: what it does, why, quick start, example, licence, how to contribute.
  3. Show HN: link to the repo; stay in the thread.
  4. DevHunt: accepts open-source projects; free listing or $49 launch week.
  5. Product Hunt: link to the repo; free.
  6. AlternativeTo: mark it open source and link the code.

Key takeaways

  • Your README is your landing page; most visitors decide there.
  • Developers try before they read; a working quick start wins.
  • Show HN suits open source because people can run it immediately.
  • Label good first issues so interested users can become contributors.
  • Don't ask anyone to star or upvote; ask them to try it.

An open source launch has no checkout page and no sign-up funnel. The repository is the product, the README is the landing page, and the conversion is someone running your install command. That makes launching it simpler in one way and harder in another: developers decide in a minute. This guide covers being ready, the README, the launch sites developers read, and turning users into contributors, drawing on GitHub's Open Source Guides and each site's rules as read on 17 November 2026. Jump to the README, where to launch or contributors.

Open Source Guides page Finding Users for Your Project
GitHub's Open Source Guides: finding users for your project.Image: Open Source Guides · Screenshot shown for commentary, 17 Nov 2026 · source

A README that converts

Checklist: A README that converts — What it does, for whom; Why it exists; Quick start; An example; The licence; How to contribute.
A README that converts
  • What it does, for whom — one sentence at the top
  • Why it exists — the problem it solves
  • Quick start — install to first result in minutes
  • An example — real input and output
  • The licence — clearly stated
  • How to contribute — a link to CONTRIBUTING and good first issues

Where to launch

SiteWhyCost
Show HNTry-able projects; candid feedbackFree
DevHuntLists open-source projects; developers vote weeklyFree listing; $49 launch
Product HuntBroad launch day; link the repoFree
AlternativeToFlag as open source, link the codeFree
A permanent project pageFound by the problem it solvesFree

Table: Where to launch an open source project (each site's own pages, checked 17 Nov 2026)

DevHunt homepage
DevHunt: open-source projects welcome.Image: DevHunt · Screenshot shown for commentary, 17 Nov 2026 · source
Hacker News Show page
Show HN: link to the repo and stay to discuss.Image: Hacker News · Screenshot shown for commentary, 16 Nov 2026 · source

Turning users into contributors

Diagram of 5 steps for turning users into contributors: 1. Label good first issues; 2. Write CONTRIBUTING; 3. Review quickly; 4. Thank publicly; 5. Invite repeat contributors.
Turning users into contributors
  1. Label good first issues — small, well-described tasks.
  2. Write CONTRIBUTING — setup, tests, style, how to submit.
  3. Review quickly — a fast first response keeps people.
  4. Thank publicly — in release notes.
  5. Invite repeat contributors — to review and maintain.

Mistakes

Checklist: Mistakes — Launching before the quick start works; No licence; Asking for stars or upvotes; Disappearing after launch.
Mistakes
  • Launching before the quick start works
  • No licence — people can't safely use it
  • Asking for stars or upvotes — ask them to try it
  • Disappearing after launch — answer issues and comments

Ready to launch?

How we know

Launch-site rules come from the Show HN guidelines, DevHunt's FAQ, Product Hunt's help centre and AlternativeTo's FAQ, read on 17 November 2026; finding-users advice from GitHub's Open Source Guides. The README and contributor checklists are our editorial recommendations.

Key terms, defined

  • Open source: software whose code is published under a licence allowing use and modification.
  • README: the main document shown on a repository's page.
  • Good first issue: a small task labelled for new contributors.
  • Licence: the terms under which code may be used.
  • Contributor: someone who submits changes to a project.

Frequently asked questions

How do I launch an open source project?

Make it installable with a quick start, write a clear README with a licence, then post a Show HN, list it on DevHunt, launch on Product Hunt and add it to AlternativeTo as open source. Stay present to answer questions.

Where should I promote an open source project?

Show HN on Hacker News, DevHunt (it lists open-source projects), Product Hunt, AlternativeTo (with the open-source flag and code link), communities around the problem, and a permanent project page.

What should an open source README include?

What it does and for whom, why it exists, a quick start that reaches a result, an example, the licence, and how to contribute.

Can I post an open source project on Show HN?

Yes, if people can try it: link to the repository or a demo, write a first comment on how and why you built it, and stay to discuss.

How do I get contributors?

Make contributing easy: a CONTRIBUTING file, labelled good first issues, quick reviews, and thanks for every contribution. Early users who hit an issue are your likeliest contributors.

Should I ask people to star my repo?

Ask people to try it and tell you what's missing. Launch sites such as Product Hunt and Hacker News forbid asking for upvotes, and the same spirit applies to stars.

Sources

  1. GitHub Open Source Guides — Finding users for your project
  2. Hacker News — Show HN guidelines (checked 17 Nov 2026)
  3. DevHunt — FAQ (checked 17 Nov 2026)
  4. Product Hunt Help Center — Build your product page (checked 17 Nov 2026)
  5. AlternativeTo — FAQ: licences and open source (checked 17 Nov 2026)
  6. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

Give your open source project a free, permanent Launchpad page found by the problem it solves, ranked by relevance and never by payment, alongside your repo.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition