The Decision to Finally Show Your Work: Demoing a Side Project Done Right

You’ve been in the lab for months, maybe years. Unpaid, unthanked, and glued to your keyboard. Now you’re ready to share your side project with the world—or at least the fine folks on r/sideproject. Congrats, you’re in the most vulnerable phase of your project. Let’s make the most of it.

This article isn’t another “just post on Product Hunt, bro” list. It breaks down the best ways to demo your project, the tools you’ll want to avoid, and how to ask for feedback that’s actually useful. Ready? Let’s talk trade-offs.

The Ritual of the “Show HN” or “Reddit Showcase” #

You might think posting on r/sideproject or doing a “Show HN” is straightforward: just hit Submit and wait for applause, right? Nope. The platform matters, the tone of your post matters, and even the day and time can affect whether you get 3 claps or 300 users.

Here’s a quick platform breakdown:

1. Reddit’s r/sideproject #

• Why it rocks: You’re among your people—the “quietly grinding on weekends” types. The feedback here is constructive without being soul-crushing. You’ll see comments like: “I love the UI, but does it handle edge cases like X?” Or the classic “Looks cool—pricing?”
• The trade-off: Redditors are kind if you keep it real. Skip the marketing buzzwords. Post with a link to your build, a few clean sentences on what inspired it, and a specific request for input (e.g., “How does the onboarding feel?”). Otherwise, you’ll get ignored or roasted for being too vague.

2. Show HN (Hacker News) #

• Why it’s intriguing: It’s like playing on Hard Mode. Hacker News skims between brutally honest and algorithm-savvy. The wins are huge—a well-received post here doesn’t just get comments; it gets traffic. Fast.
• The trade-off: Go in wearing armor. Criticism can be overwhelming, especially if your tech stack isn’t rock solid. (I once posted a Python-based web tool, and one top comment was just: “Node.js is faster and easier.”) Consider sharing a simple walkthrough of your unique approach because generic pitches won’t fly.

Screencasts vs. Live Demos: Which One? #

Spoiler: Don’t make people install your thing just to see what it does. You’re asking a lot from strangers on the internet.

Screencasts: Dependable & Digestible #

A 2-minute video solves so many problems. You can use something like Screenity (free) or Camtasia ($199 one-time). The goal is to take users on a journey:

1. Here’s what the problem looked like.
2. Here’s what I built to solve it.
3. Look at it working in real life.

Live Demos: Use Sparingly #

Some folks swear by live demos, and they can be magical—if your app is stable. But ask yourself: would you join a stranger’s stream just to watch them fumble through setup issues? If you must go live, Zoom or Google Meet is fine. Don’t overproduce it; people care more about the product than your PowerPoint slides.

Pricing Feedback: Handle With Care #

If your project is paid (or freemium), you’re about to step on a minefield—pricing opinions. r/sideproject has a weird vibe here. People will tell you:

• “Why isn’t it $0? Just open source it.”
• Or the opposite: “Why charge $5? Make it $19 for the premium feel.”

Both are useless unless your target audience is exactly these commenters.

Here’s what worked for me: explain your why. For my previous SaaS side project, I said, “It’s $10/month because hosting on Linode costs me $30, and I need coffee too.” That context heads off more nonsense than you’d expect.

Also, keep tools like Converkit handy. Or Google “Freemium SaaS Converter” for calculators that help you balance trials, churn, and lifetime value. Real numbers quiet the peanut gallery.

FAQ (For the Perpetually Conflicted Side Project Micromanager) #

How polished should my project be before sharing it? #

Not very. A functional MVP is fine. r/sideproject loves scrappy builds. That said, basic UX matters: if buttons don’t work or your login form breaks, do one more QA pass before hitting “Post.”

What’s the best day/time to post feedback requests? #

Weekdays around 10 AM EST work well. Avoid weekends—that’s when engagement dips as people are living offline lives (how dare they?).

Should I share my source code? #

Totally optional. If you’re after bug-hunting feedback, sure. If you’re testing monetization or SaaS ideas, skip it.

Okay, you’re ready. Post, learn, and—importantly—don’t overthink the trolls. Feedback is data. Apply what helps, ignore the noise, and keep shipping.