Get Product Feedback

Get Product Feedback from the r/SideProject Community

r/SideProject is a community built around giving and receiving feedback on side projects. Members actively look for projects to review and take pride in giving useful, constructive criticism.

Get Started See Community Approach

Related Resources

r/SideProject Marketing Guide

Complete guide to marketing on this subreddit

How to Get Product Feedback

General guide to solving this problem on Reddit

Visit r/SideProject on Reddit →

See the community and current discussions

Signs of Success

You'll know this approach is working when you see:

Receiving feedback that changes your product direction
Discovering user experience issues you were blind to
Getting specific suggestions you can implement immediately
Building relationships with potential early adopters

Community-Specific Approach

How to tackle this problem specifically in r/SideProject.

Frame your feedback request clearly

The community appreciates knowing what kind of feedback you need. UX feedback? Pricing thoughts? Technical architecture?

Example

"Looking for feedback on the onboarding flow" gets more focused responses than "thoughts?"

Show your work

Include screenshots or a working link. r/SideProject members want to interact with your project, not just read about it.

Share your decisions and doubts

Explain why you made certain choices and what you're uncertain about. This invites more thoughtful feedback.

Example

"Chose this pricing model because X, but worried about Y" sparks useful discussion.

Reciprocate generously

Give detailed feedback on other projects. The community notices contributors and engages more with their requests.

Implement and share changes

When you act on feedback, share the update. It shows respect for the community's input.

Post Strategies That Work

Real post formats that resonate in r/SideProject for this specific goal.

Focused feedback request

"Need feedback on [specific aspect] of my side project. Built [product] for [audience]. Specifically unsure about: [questions]. Link: [URL]"

Focused questions get focused answers. Easier for people to help when they know what you need.

Roast request

"Roast my side project: [URL]. Built [description]. Be brutal - what would stop you from using this?"

Inviting criticism gives permission for honesty. Often surfaces issues friends won't mention.

A/B decision post

"Side project decision: [Option A] vs [Option B]. Here's my thinking: [context]. Which would you choose?"

Binary choices are easy to respond to. Gets concrete opinions rather than vague feedback.

Avoid These Mistakes

Common pitfalls when tackling this problem in r/SideProject.

❌ Asking for feedback without a working product

r/SideProject expects something to try. Ideas and mockups get less engagement than working projects.

Better approach

Even a basic MVP with core functionality. The community wants to interact with your project.

❌ Getting defensive about criticism

The community shares honest opinions. Arguing with feedback discourages future responses.

Better approach

Thank everyone, ask follow-up questions, and genuinely consider the feedback.

❌ Treating feedback as validation seeking

Members can tell when you want praise, not critique. They'll disengage or give generic responses.

Better approach

Actively seek what's wrong. Ask "What would make you leave?" not "Do you like it?"

Frequently Asked Questions

Common questions about get product feedback on r/SideProject.

Everything from UX and design critiques to technical suggestions and business model feedback. The community includes designers, developers, and product people.