What does community-driven product development actually look like? Here's our story.
We're live on Product Hunt today with the Second Brain desktop app. I wanted to share what this journey has actually looked like.
Every feature in this product came from a comment. Not a roadmap. Not a strategy session. A comment from someone in this community who told us what was missing.
That's what community-driven development actually means to us. Not a marketing line. The real thing.
If you've been part of that journey, today is your day too. Come check it out, share your thoughts, tell us what we should build next.
Let's celebrate what we built together.
16 views
Replies
just left a question on the desktop app launch too - genuinely like that the whole reason it exists is people saying git/terminal was too much friction, not a roadmap item someone dreamed up internally. curious if you've ever had two people ask for opposite things and how you decide which one actually becomes a feature.
the frame that lands here is 'a comment from someone who told us what was missing.' most teams collect feedback and file it under 'feature requests.' the ones that ship correct products treat those comments as evidence of a gap in the model, not as items on a wishlist. thats the distinction. the desktop app existing is the community's receipt that you actually listened. congrats on the ship, going to poke around and report back what breaks.