I've shipped three indie apps. The code was fine. The biggest thing I got wrong each time? I had no idea what was actually broken until it was too late.
Not because I didn't ask for feedback — I asked constantly. But every channel I tried had a fatal flaw.
The feedback problem nobody talks about
You post your project. You get 2 upvotes, maybe 3, and a comment asking if it works on Android. The feedback is random, unstructured, and from people who may not be your users at all. There's no incentive for anyone to go deep.
Product Hunt
It's a launch-day network contest. If you don't have 500 people ready to upvote on the day you launch, you're invisible by noon. The feedback in comments is usually "congrats on the launch!" — not "your onboarding is broken."
Friends and family
They love everything. Every time. It's completely useless.
Asking on Twitter / build in public
You get engagement from other founders who also want feedback on their apps. Everyone's broadcasting, nobody's giving structured critique. The dynamic is social, not evaluative.
What actually happens when feedback fails
You find out your onboarding was confusing 3 months after launch, when your retention numbers don't make sense. You realize your value prop was buried after 500 people visited and 490 left in 30 seconds. You learn your core flow broke on mobile only when someone DMs you about it.
I've been there. It's a slow, expensive way to learn.
What I built
I started working on Stackrate — a dev-to-dev peer review platform for indie apps.
The mechanic is simple:
- Submit your app with a specific review request — UX, onboarding, value prop, performance, or all of it
- Review another app to earn credits
- Spend credits to get your own app reviewed
- Reviewers verify via GitHub or App Store — only people who actually ship software can review
- Bad reviews lose credits — quality is enforced by the system, not just hoped for
It's closer to code review than to Product Hunt. Structured, peer-driven, accountable.
Why the credit mechanic matters
Most feedback platforms fail because there's no incentive alignment. Giving good feedback takes time. Nobody does it for free with strangers.
The credit system solves this. You have to give to receive. And because your credits are on the line, you have an incentive to give feedback that's actually useful.
Why verification matters
Random opinions are cheap. I don't want to know what someone who's never built software thinks about my UX. I want to know what a developer who has shipped something thinks — because they understand the tradeoffs, the constraints, and the context.
GitHub and App Store verification filters for that.
Where it stands
Stackrate is pre-launch. The waitlist is live at stackrate-waitlist.netlify.app. I'm onboarding developers in small batches.
If you've ever shipped something and gotten nothing useful back — this is for you.
Would love your thoughts in the comments. Especially curious: what's the most useless feedback you've ever gotten on a project?
Top comments (0)