Where to Post Your AI-Built Project So People Actually Respond

You shipped something with Claude, Cursor, or another AI coding tool. Now it sits on a URL nobody has visited. The next problem isn't building. It's finding out whether the thing you built works for someone besides you, and that takes real feedback, not just eyeballs.

Across Hacker News, Product Hunt, Peerlist, Indie Hackers, and Reddit's r/SideProject, one pattern shows up again and again. The platform you choose matters less than the specific thing you post on it. A bare link gets a passive glance. A specific ask, backed by a fast, personal reply to whoever responds, gets a real answer.

The problem: views aren't feedback

A star, an upvote, or a "cool project!" comment tells you almost nothing. It doesn't tell you whether the onboarding flow confused someone. It doesn't tell you whether the price felt fair, or whether a stranger could tell what your project does in the first five seconds. You already shipped. You don't need another tutorial on how to build. You need to know which specific action, on which platform, produces a real answer instead of a passive view.

What the evidence shows

Hacker News rewards a technical backstory, not a pitch. Hacker News's own Show HN guidelines ask you to state clearly what your project does and link any earlier related threads. Add backstory as your first comment if it doesn't already appear at the top of the post. A breakdown of one real dev-tool launch found the founder personally answered 53 comments in the thread. That volume of direct reply, not the initial post, is what turned the thread into feedback.

A separate guide on Hacker News marketing draws the line precisely. A useful first comment names who you are and the specific problem or constraint behind the build. It says what kind of feedback would actually help. A comment that asks for support, or turns the thread into a sales pitch, does the opposite. Timing matters too: one practitioner guide recommends posting Tuesday through Thursday between 8 and 11 a.m. Eastern, then answering every comment for the first two hours.

Product Hunt trades reach for a longer runway you have to build yourself. Product Hunt can still send real numbers. One 2026 playbook reports that a top-10-of-the-day finish takes roughly 150 to 400 upvotes, and a well-prepared launch can drive 5,000 to 20,000 visitors and 300 to 1,000 signups in a single day.

Two other independent 2026 guides converge on the mechanic behind those numbers. A "hunter list" of 100 to 200 people matters more than your total follower count, because Product Hunt's ranking weighs engagement velocity and comment quality, not raw vote totals. Buying votes or joining vote-swap groups gets flagged by the platform's spam detection instead of helping. The payoff window has also shrunk: residual traffic after launch day has gone from one to two weeks in 2022 down to two to four days in 2026, per the same source.

Peerlist's Launchpad is built for feedback depth over reach. Every project submitted to Peerlist's weekly Launchpad gets featured. One independent breakdown of the Launchpad reports that ranking stays randomized for roughly the first two days, so a small account isn't buried right away. Peerlist's own guidelines describe the format as a "soft launch," meant to collect feedback and iterate, not a one-shot traffic event. You get far fewer visitors than Product Hunt. Independent accounts of using it note that the comments tend to be substantive, because the audience is other builders rather than passersby chasing a badge.

Indie Hackers and Reddit both punish the passive post. In Indie Hackers' "how did you get your first 100 users" thread, founders repeatedly describe direct outreach as what actually produced their first real users. Friends, coworkers, and daily posting on Twitter and Reddit come up more than any single platform listing. On Reddit's r/SideProject, two independent trackers of the subreddit's posting norms agree on the same shape. A post needs to explain what you built, why, what tools you used, and what specific feedback you want. A bare landing-page link "won't get traction," and ignoring the people who do comment reads as spam-adjacent behavior. Reposting the same project before you have a real update lands the same way.

VibeCoding.Builders runs the same kind of listing itself. The /builders directory and /projects showcase on this site work on the identical principle. A builder profile with real context earns more attention than a bare link. The "Build to Launch Friday" interview slot exists to make one builder's story visible to the rest of the community for a week, not just a moment.

How to apply it this week

1. Pick one platform whose stated audience already fits your project, not the platform with the biggest number attached to it. A developer tool aimed at other engineers fits Hacker News or Peerlist better than Product Hunt's broader, more general audience.
2. Write a specific ask before you post it anywhere. Name the one thing you want checked, such as onboarding, pricing, or a particular screen, instead of a generic "thoughts?" A specific ask is also what separates a useful Show HN comment or Reddit post from one that reads as a pitch.
3. Block real time to reply, not just to publish. Two hours of fast, personal replies right after posting is the mechanic behind every platform above. It shows up in Hacker News's comment window, Product Hunt's early-wave engagement, and Peerlist's soft-launch framing alike.
4. Decide what counts as a real answer before you post. That way an upvote count doesn't get mistaken for validation. A specific critique of your onboarding flow is a real answer. A star with no comment is not.

Limits: feedback from builders isn't feedback from your customer

Every platform above pulls its commenters mostly from other builders, people who ship AI-assisted projects themselves. That's exactly why the feedback tends to be specific and technical. It's also a real limitation. If your project's actual customer is not a builder, such as a small-business owner or a teacher, a thread full of engineer commentary can validate the wrong thing.

One founder's account of shipping a consumer app put it directly. Build-in-public followers are frequently not your users. A Reddit survey plus direct conversations with the intended audience shaped that product's real roadmap more than the platform comments did. A separate explainer on the same tradeoff makes the point from the other direction. Public building creates real distribution and trust, but it doesn't replace finding and listening to the people who will actually use the thing. Treat every showcase and community on this list as one input, not the whole answer, when your target user isn't in the room.

Recommended next action

Before your next post, write down two things. Name the platform whose audience already overlaps with your intended user, and name the one specific question you want answered. Post once, with that question in the first comment or in the post itself, and hold two hours open to reply to everyone who responds. If nobody who replies looks like your actual target user, treat that as a signal to go find that person directly, rather than post again in the same place.

Sources

• Launch HN Instructions — news.ycombinator.com/yli.html
• Peerlist — peerlist.io
• Peerlist Project Spotlight FAQs and Guidelines — peerlist.neetokb.com
• VibeCoding.Builders Builders directory — vibecoding.builders/builders
• VibeCoding.Builders Projects showcase — vibecoding.builders/projects
• "How to Launch on Product Hunt and Get 500+ Upvotes in 2026" — usamasoft.com
• "Product Hunt Launch Guide 2026: How to Get to #1 Without Buying Upvotes" — welaunch.sh
• "How to Get Upvotes on Product Hunt (2026)" — phlaunchkit.com
• "How to launch a dev tool on Hacker News" — markepear.dev
• "How to Launch on Hacker News and Get Traction (2026)" — okara.ai
• "Hacker News Posting Guide: Rules, Show HN, and Timing" — syften.com
• Indie Hackers, "What are you building? and how did you get your first 100 users?" — indiehackers.com
• "r/SideProject Self-Promotion Rules 2026" — redditmaster.com
• "r/SideProject Promotion Rules: Verify Before Posting (2026)" — redditgrowthdb.com
• "Your Build-in-Public Followers Are Not Your Users" — hackernoon.com
• "How to launch a Product on Peerlist.io launchpad?" — tetriz.io
• "Building in public: Is this the right approach for your startup?" — mercury.com