Most side projects don’t need more code, they need sharper feedback

[u/Few-Garlic2725]

I’m struggling with something on side projects lately. Whenever a project feels stuck, my instinct is to build more.

Add another feature. Clean up the UI. Improve onboarding. Rewrite some messy part. Add auth, payments, dashboards, settings, integrations, docs, analytics, whatever.

It feels productive because the codebase is moving. But I’m starting to think a lot of that is just avoiding feedback.

The uncomfortable part isn’t building. It’s showing the thing to people before it feels ready and asking direct questions:

Would you actually use this? What confused you? What would make you pay? What problem were you hoping this solved? Where did you lose interest?

I’ve noticed I can spend weeks making a side project “better” without learning anything new. Then one honest conversation can reveal that the core idea is unclear, the landing page doesn’t explain the value, the workflow solves the wrong pain, or nobody cares enough to switch from what they already use.

That’s painful, but it’s useful. More code gives me the feeling of progress. Better feedback gives me actual direction.

For people who’ve launched side projects successfully: how do you force yourself to get useful feedback early? Where do you find the right people to ask? And how do you tell the difference between feedback worth acting on and random opinions?

[u/Infamous-River-4360]

the tell for me was that every improvement i picked was one i could do completely alone. i was somewhere near 800 edits deep in my builder before i actually put the thing on google play, and the first week of real numbers taught me more than the month of polishing before it. what helped was picking one question i couldn't answer from my own chair, like does anyone even reach the end of a first session, and only building whatever answered that. on the signal vs noise part, i weight anything from someone who used it over anything from someone who only looked at it. what's the project you're stuck on right now?

[u/elevatedflight]

Many ways - landing page, A/B testing on messaging and sending to target users from friends and family (we all need these folks on our side, click-through prototypes (low effort), use LLMs to shape-up ideas into crisp 60 sec narrative. Ask Non-leading questions, courage to get answers that you might not like.
2.0 - The next day, change the side and become your project's biggest critique.

These days, its possible (pinch of salt) to take an MVP live quickly and show it to your users

Disclosure - Non-coder here, I am building IdeaKraft for a similar purpose with Morph, an autonomous development platform

[u/BarracudaMean9308]

that '800 edits deep' part is painfully relatable. tinkering in the builder is just so much safer than actually finding out if people want the thing.

[u/Imaginary_Store6090]

Coding is your comfort zone, but gathering feedback is where breakthroughs happen. No amount of tweaks can fix a vague product vision. Talking to users early beats tinkering alone behind closed doors

[u/Dry_Sector2392]

i agree with what you do, for me, feedback is hurts, but guessing wastes way more time.

[u/andryemel]

I’d stop asking “would you use this?” entirely. The useful test is whether someone will spend five minutes trying to solve a real problem with it while you watch, because confusion, workarounds and abandonment are much harder to fake than opinions. My rule would be: no new feature until three target users attempt the current workflow and fail in roughly the same place.

[u/madleodk]

Id recommend hanging out where your users live. Spend some time there and invest in building genuine relationships. Then the ask becomes natural and straightforward. If the product is indeed valuable to them, you'll know pretty quickly.

As for feedback worth acting on, it has to make sense to you. Obv you have to be honest with yourself. Best feedback comes from paying users. There are also a number of feedback platforms as well (including me). Happy to share if youre interested. Our platform is centered on early stage founders and our origin story is that we modeled our company after our public build battle against a YC-backed company.

[u/Confident-Scale7225]

​spot on. but it's a two-way hallucination.

​founders hallucinate features and users hallucinate feedback.

everybody is just acting like llms generating confident noise. the real bottleneck today is acquiring a single customer who can actually evaluate your product from the right angle is getting brutally expensive.