Good advice. Do you think the part of point two about building every feature request might be a bit risky for some solo folks?
It’s easy to get carried away building every request, especially with early adopters who likely aren’t actually invested yet but may be excited about their own vision for it.
My personal experience is that too much of it leads to the product becoming a sort of shapeless, unwieldy ooze. Or perfect for one customer and few others. Some things can be tough to undo later too, so you might end up supporting them a lot longer than you’d like.
I agree there needs to be a way to fit it into the overall product direction. Solving these on a case-by-case basis is important and part of the job.
When I first started, getting customer reviews was my north star, so i would add any feature and hide them under "advanced" if they were ridiculously long-tail. Still worth it for the review and positive experience even if you hide the feature...
How do you know what feature request to add, then? The ones suggested by multiple users independently?