Where to Post Your App in 2026: A Realistic List

Every list of "50 places to post your app" has the same problem: it treats all 50 as equal, and they're not. Most will send you a trickle or nothing; a few will send you real people; one or two will quietly compound for years. Here's the honest version of that list, organized by what each channel is actually good for.

The framing that makes all of this work: posting your app is not distribution, it's a set of experiments. Each post tells you something about where your users live. Expect single-digit results from most channels and treat anything better as a finding worth doubling down on.

Launch platforms: one good day

Product Hunt and similar launch platforms give you a launch day — a burst of traffic, some signups, a badge for your landing page. What they mostly don't give you is durable, ongoing users, unless your product happens to resonate with the early-adopter crowd that lives there.

Worth doing? Usually yes, once, when the product can survive strangers: the value shows up fast and onboarding doesn't need you standing next to the user. Prepare a clear tagline, a real demo or GIF, and be present in the comments all day. Just don't build your plan around it — a launch platform is a spike, and spikes decay.

Hacker News: high risk, high signal

"Show HN" can send more traffic in an afternoon than everything else on this list combined — or it can sink without a single comment, and both outcomes are normal. What HN rewards is genuinely interesting work described plainly: no marketing tone, real technical details, honest limitations up front. What it punishes is hype.

Post once, at a reasonable hour, with a title that says what the thing actually is. Answer every comment, including the harsh ones, without getting defensive. Even a modest thread is useful: HN commenters will articulate objections to your product that politer communities won't.

Reddit and niche forums: where your users already are

This is the channel most indie devs do wrong. The move is not "post my app in twenty subreddits" — that gets you removed and occasionally banned. The move is: find the two or three communities where your users (not other developers) hang out, participate for real, and share the app in the way each community's rules allow — many have dedicated self-promo threads or flair.

Lead with the problem you solved and the story of building it. "I got tired of X, so I built Y, here's what was hard" consistently outperforms "Check out Y!" in any forum with humans in it.

Directories and showcases: slow, compounding, cheap

Directory listings rarely produce a spike. What they produce is a page that exists forever: a backlink, a description search engines can find, and a steady trickle of people who browse directories because they like trying new things. That trickle costs you ten minutes of form-filling, once. Over a year, a handful of good listings quietly beats most one-day spikes.

Do a batch of them in one afternoon. Naturally, we'd love to be one: submit your app to TryMy.App — it's free, human-reviewed, and your listing links straight to your site.

Skip the sketchy "500 backlinks" directory-blast services. Search engines discount that pattern, and the sites are graveyards.

Builder communities: trade effort, not posts

Communities of fellow makers won't be your customer base (unless you're building dev tools), but they're the best source of early testers, feedback, and launch-day support. The economics are reciprocal: the people who get value from these spaces are the ones who give first. Favors.dev makes that explicit — indie builders trade favors like "test my app" or "share my launch," earn points for helping, and spend them when it's their turn to launch.

However you do it, the principle is the same: five thoughtful pieces of feedback given buys you five back, and five real testers beat five hundred impressions.

Newsletters and curators: borrowed audiences

Plenty of niche newsletters round up new tools, and a mention in one that matches your audience can outperform a big general-purpose one. The pitch is short: two sentences on what the app does and who it's for, a link, and an offer to answer questions. Curators want to fill next week's issue; make their job easy. Expect most pitches to go unanswered — that's the normal hit rate, not a verdict on your app.

Your own channels: the long game

Everything above borrows someone else's audience. The channel that compounds hardest is your own: a blog post that ranks for the problem your app solves, a build log people follow, an email list of everyone who ever tried the app. These are slow — months, not days — which is exactly why most people skip them and why they keep working for the people who don't.

If you only do one thing here, write the article your future user would search for, and put your app in it as the answer.

The channels compared

Channel	Effort	Shape of the traffic	Half-life	Best for
Launch platforms	High, one day	Sharp spike	Hours	A concentrated first day
Hacker News (Show HN)	Medium	Spike or silence	~24h	Developer tools with a real technical story
Reddit / niche forums	Medium, ongoing	Steady trickle	Days	Reaching people with the problem
Directories & showcases	Low, once	Slow drip	Months–years	Compounding discovery and backlinks
Builder communities	Medium, reciprocal	Small but engaged	Ongoing	Honest feedback and launch-day support
Newsletters / curators	Medium pitch	One-off burst	Days	Borrowing an audience that already trusts someone
Your own writing	High, compounding	Slow then durable	Years	Being found next year without posting again

The column that changes strategy is half-life. Launch platforms and Hacker News are events; directories and your own writing are assets. Most solo developers over-invest in the first pair and under-invest in the second, because events produce a visible number on the day and assets produce nothing for six weeks.

The honest allocation is to do the events once, properly, and then spend the following months on the things with a half-life measured in years.

Two shortcuts worth taking

For the directory row, don't assemble the list yourself. Favors.dev maintains a running startup launch directories list — submitting to a batch of them in one sitting is a couple of hours that keeps paying out, which is exactly the profile that column describes.

For the community row, the fastest way to reach people who actually try things is a community built around building. Vibe Coding is Life is a 320,000-member group of people shipping software, and a work-in-progress post there reaches an audience that clicks demos for fun. Same rule as every community below, though: be a member before you're a poster.

A realistic sequence

1. Before launch: get listed in a few directories, join two user communities and one builder community, and start the follow-up habit from your first-100 push.
2. Launch week: one launch platform, one Show HN if the product fits, one story-style post in each community where you're already a citizen.
3. After: pitch two or three niche newsletters, publish one problem-focused article, and check which channel actually sent people who stuck. Do more of that one.

The realistic summary: launch platforms give you a day, communities give you people, directories give you permanence, and your own writing gives you a future. Use all four, expect modest numbers from each, and let the results — not the listicle — tell you where to spend next month.