Where to share your vibe coded app (so people actually see it)

There’s a particular silence that follows shipping your first vibe coded app. You post the link, refresh a few times, and get two likes: your sister and a bot. It isn’t that the app is bad. It’s that a link on its own gives nobody a reason to care.

The good news is that the fix is mostly about where you post and how you frame it, not about building something cleverer. People love seeing what someone made with AI, especially when they can see how. You just have to show them.

First, make it worth clicking

Before you share anywhere, spend twenty minutes on these. They do more for your numbers than any posting time or hashtag.

• One sentence that says what it does for someone. “Invoices that chase themselves” beats “an AI-powered invoicing platform”. If you can’t say who it’s for in one line, nobody else will either.
• A screenshot or a ten second clip. Most people decide from the image. Show the moment it’s useful, not the login screen.
• A link that works without signing up. A demo account, a guest mode or a video. Every extra step loses most of the people who would have loved it.
• The build story. What you asked the AI, where it nailed it, where you had to step in, how long it took. This is the part people actually want, and it’s the part almost nobody writes.

Where to share it

Vibers

We’re biased, but this is what it’s built for. Your project gets a page with the screenshots, the tools you used, the build time and your story, and it lands in a feed of people who came specifically to see what others built with AI. Upvotes put good work on the leaderboard and the tool pages, and everything you post builds a portfolio that clients can hire you from. If there’s a challenge running that fits, enter it: entries get far more eyes than a normal post.

Show HN (Hacker News)

Post it as “Show HN: [name], [what it does]”. It only works for things people can try right now, and the crowd is technical and blunt. Be in the comments for the first couple of hours and answer everything honestly, including “how much of this did AI write?”. Do that well and a Show HN can bring thousands of visits in a day. Do it badly and it sinks without trace.

Product Hunt

Better for polished products than weekend experiments. Launches run on a daily cycle, so prepare your images and first comment in advance and launch early in the day (Pacific time). It rewards having people ready to try it and leave genuine comments, so it suits your second or third project better than your first.

Reddit

r/vibecoding is the obvious home, and r/SideProject welcomes “I built this” posts. Read each subreddit’s rules first: most hate drive-by links. Write a post that tells the story and asks a real question (“would you use this for X?”), with the link in it, not a link with one line of text.

X (build in public)

Post the clip, the one-line pitch and the build time, then reply to your own post with the story: the prompt that worked, the bug that took three hours, the moment it clicked. Tag the tools you used; their teams often repost good work. Consistency beats virality here. Ten honest posts about one project usually outperform one clever thread.

Your own corners

The group chat, the Discord you’re in, the colleague who complained about exactly the problem your app solves. Small audiences who know you give the most useful feedback, and they’re the most likely to tell someone else.

Turn attention into something that lasts

A spike of visitors fades in a day or two. What stays is anything you gave people a reason to come back to.

1. Collect a way to reach people. An email field, a waitlist, a follow. Without it, your launch is a one-off.
2. Post the update, not just the launch. “Week 2: added the thing three of you asked for” is a second launch, and it shows you listen.
3. Keep the portfolio in one place. Every project on your Vibers profile makes the next one more believable, to users and to anyone thinking of hiring you.
4. Thank the people who tried it. Reply to every comment you can in the first week. It’s the cheapest marketing there is, and it’s how strangers become regulars.

Common mistakes

• Sharing too early. If the first screen is broken on mobile, that’s what people remember. Test on a phone first.
• Hiding that you used AI. People respect “I built this with Claude in a weekend”. They don’t respect finding out later.
• Asking for upvotes instead of feedback. Most communities can smell it, and some will bury you for it. Ask what they think.
• Posting everywhere on the same day. You can’t answer every comment in six places at once. Stagger it over a week.