Your Side Project Doesn't Need More Compliments. It Needs Better Feedback. Imagine this.
You've spent three months building a side project. You finally share it with friends. Their response? "Looks amazing!" "Great work!" "Keep going!" You feel good for a moment. But then you realize something: You s
You've spent three months building a side project.
You finally share it with friends.
Their response?
"Looks amazing!"
"Great work!"
"Keep going!"
You feel good for a moment.
But then you realize something:
You still have no idea whether anyone would actually use your product.
I've experienced this problem myself, and I think it's one of the most overlooked challenges in independent software development.
The problem with asking people for feedback
Most developers know they should get feedback before spending months building something.
But getting useful feedback is surprisingly difficult.
Here are three common problems.
- People are too polite.
Friends and family often don't want to hurt your feelings. They tell you what sounds encouraging rather than what you need to hear.
- Questions are too vague.
Asking "What do you think of my website?" doesn't give people much direction.
You'll probably receive answers like "Looks good" or "Nice design."
- Developers don't have time to help each other.
Everyone is busy building their own products. Finding people willing to explore your project and give thoughtful feedback takes effort.
A better way to ask for feedback
I've started thinking about feedback differently.
Instead of asking:
What do you think of my project?
Try asking:
- Would you understand what this product does within 10 seconds?
- What's the first thing you'd change?
- What would stop you from using it?
- Which feature would you remove?
- Would you recommend it to someone? Why or why not? The difference is simple.
Specific questions produce more useful answers.
And there's another important point: feedback should be honest, not automatically positive.
So I started building Critique
Insert your actual platform screenshot or walkthrough video here.
I wanted to experiment with a platform built around this idea.
That's why I created Critique.
The concept is straightforward:
- Share your project.
- Ask one focused question.
- Let other people explore it.
- Collect honest feedback. The goal is to make giving and receiving feedback easier for independent developers.
Critique focuses on human feedback rather than AI-generated reviews.
It's also open source:
- Website: https://critique.page
- GitHub: https://github.com/BistaDinesh03/critique Building this while studying in Japan A little about me.
I'm originally from a small farming village in Humla, Nepal. I moved to Japan to study, and I'm currently an IT engineering student.
Alongside my studies, I've been building independent software projects.
One thing I've learned is that writing code is only one part of building a product.
Understanding people, finding users, and discovering whether you're solving a real problem can be much harder.
Critique is my attempt to work on that problem.
And honestly, I'm still figuring it out.
I want to challenge other developers
I have a few questions for people building side projects:
- When was the last time someone gave you genuinely negative feedback about your product?
- Do you prefer feedback from other developers or actual potential customers?
- Would you spend three minutes reviewing another developer's project if it helped you receive feedback on your own?
- What makes you ignore a feedback request? I'd particularly like to hear from developers who have launched products but struggled to get meaningful user feedback.
If you're interested, explore Critique and tell me what you genuinely think.
I'd rather hear that the idea is bad than receive another "Looks great!"
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.