When I started building my side project, I thought getting people to visit the website would be one of the hardest parts.
I was wrong.
Getting visitors was difficult, but getting someone to actually do something after visiting was a completely different challenge.
Someone could open your website, look around for 20 seconds, and leave.
No feedback.
No explanation.
You don't even know what they thought.
And as a developer, that's frustrating.
I wanted honest feedback, not another analytics dashboard
I had been building projects and realized something:
We spend hours writing code, choosing technologies, designing interfaces, and fixing bugs.
But when it comes to answering one simple question—
Does this actually make sense to another person?
We often have no idea.
Friends might say your project looks great. Other developers might leave a GitHub star.
But neither necessarily tells you what needs improving.
I wanted a place where developers could share a project, ask one focused question, and receive actual opinions from other people.
That's how I started building Critique.
Then I discovered I was creating the same problem myself
I looked at my analytics.
Here were some of the numbers:
- 545 unique visitors
- 119 feedback starts
- 35 recorded feedback submissions
- 23 project submissions
Those are event counts, not a perfectly deduplicated user journey, but they showed me something worth investigating.
People were finding projects. Some were interested enough to start writing feedback.
But far fewer completed the process.
I started asking myself:
Why should someone need to create another account just to help another developer?
I had made the process harder than it needed to be.
I listened and changed the experience
I asked people about the problem and received some honest responses.
One person pointed out that casual visitors shouldn't have to create an account just to leave feedback.
Another suggested that an optional email field could be enough for people who wanted a follow-up.
Those comments made me reconsider the experience.
So I changed it.
Now, people can browse projects and submit feedback without signing in.
Publishing your own project still requires an account, but helping someone else doesn't.
It sounds like a small change.
But sometimes removing one unnecessary step can make a much bigger difference than adding another feature.
What is Critique?
Critique is an open-source platform built around one simple idea:
Ask one question. Get real answers.
You can:
- Share a side project, website, or open-source tool.
- Ask one specific question about what you want to improve.
- Discover projects built by other developers.
- Give honest feedback without creating an account.
The idea isn't to collect likes or followers.
It's to help builders get opinions they can actually use.
I'm still learning
I don't want to pretend I've solved the feedback problem.
Critique is still growing, and I'm still learning what makes people willing to share their opinions.
Maybe the questions need to be better.
Maybe people need more reasons to explore projects.
Maybe we need to make giving useful feedback even easier.
I don't know all the answers yet.
But I'd rather build something, listen to real people, and improve it than assume I know what developers want.
I'd like to ask you something
Imagine you launch a side project tomorrow.
You can ask other developers one question about it and get honest feedback.
What would you ask them?
And what's the biggest reason you don't usually leave feedback on other people's projects?
I'm building Critique around this idea. If you're curious, take a look, explore a few projects, or leave someone a piece of feedback.
No account needed to help.
The project is also open source:
https://github.com/BistaDinesh03/critique
I'd genuinely like to hear what you think.
