One thing I keep struggling with while building products is figuring out which features are actually worth spending time on.

I sometimes come up with ideas that sound great, but then I wonder whether anyone would really use them. I also don't want to spend days building something that people don't actually need.

I'm trying to get better at understanding user needs before jumping straight into coding.

For those who've built and launched products, how do you usually decide what to work on next? Do you talk to users, look at feedback, or just build your ideas and see what happens?

Recently, I asked how much you trust AI agents.

When it comes to finances, you said you don t.
With health data, you don t either.

But now I have a different question.

Watching a massive wave of new signups roll in every morning feels amazing until you check your active user retention and realize 90% of them never even finished onboarding.

We spent months tweaking our top-of-funnel acquisition completely ignoring the massive holes where people were dropping off.

Shifting our entire team's focus from raw registration numbers to weekly active milestones was painful but it saved our product.

What metric finally made your team stop chasing signups and fix activation?

In most teams I talk to, the content exists: videos, docs, a Notion page. The problem is that half of it never gets finished, and nobody notices until something goes wrong. What s worked for you? Shorter formats, deadlines, nudges from managers, something else?

We finally had to kill our anonymous, no-account-required tool because bot traffic was quietly draining our API budget. Now, anyone who wants the core feature has to make a free account first. The issue is that the people losing the friction-free experience are anonymous visitors we have zero contact info for so our landing page announcement feels like shouting into the void.

If you've ever gated a previously open utility, how did you explain the change without sounding defensive?

I built a couple of web-apps that barely have or have none users, and because of that I'm really stuck right now. I can't get any feedbacks on how the web-app is or how could I improve it. Could someone share a working advice?

There is a massive danger in letting your most active users dictate every new feature on your backlog. We built advanced automation tools for them last quarter, but our retention actually dropped because regular users felt the app became too bloated and hard to use. Finding that balance between power user depth and casual user simplicity is brutal. How do you decide when to say no to heavy feature requests?

Comment awards

One of the reasons we love our community so much is that genuine feedback is not hard to come by. Now, you can get recognized by makers for your helpful suggestions, finds, and witty comments.

Makers - we encourage you to hand out these awards (3 per launch) and share the love with your supporters. Do so by reviewing your launch post comments and clicking award on the ones you d like to highlight.