Genius.ly provided something I’ve been looking for, which is a direct connection to the users of my product to capture their feedback and ideas. The product made it easy to plug in to my website and start to collect real insight from my users.
The integration with Linear allows me to easily process the enhancements.
I’m looking forward to the feedback so I can identify the features my users are requesting as well as providing the feedback loop a user will appreciate.
The integrations could be more of a step-by-step setup.
This is the first solution I have come across that provides this.
Launching a mobile app soon and this is exactly the phase where feedback is scattered across app store reviews, DMs, and random messages so the timing of seeing this is funny. Practical question: is the feedback trigger web-only right now, or is there a way to embed it in a React Native app? Most tools in this space treat mobile as an afterthought and that's where the context-capture would matter most for me.
@cannetjam You’ve found the exact edge we care about. Right now, Genius is web-first. I don’t want to call a wrapped web view “mobile support” and pretend the problem is solved. A proper React Native experience is the next frontier because you’re right: on mobile, context isn’t a nice-to-have. It’s the difference between useful feedback and a mystery. What kind of application are you building? I’d love to understand your launch flow and potentially build this around a real use case instead of a roadmap assumption.
Dropped the widget into a side project and the context capture actually felt useful, not just another inbox dump. Liked that it turns comments into a score you can sort by, makes triaging way less painful.
@onurmesutgil That’s the distinction. Most feedback tools collect opinions. Genius is built to help you decide what deserves attention. The score turns a crowded inbox into a signal you can actually act on. What would you want that score to weigh most: frequency, customer value, urgency, or something else?
Love how the trigger stays invisible until it's actually useful. Most feedback widgets feel like clutter, but this one earns its place by keeping the surrounding context intact instead of pulling users out of flow.
@hseyinbala8d1p That was the idea. A feedback trigger shouldn’t ask for attention. It should wait until the moment it can earn it. Keeping the context intact means the user stays in the experience, and the team gets something they can actually use. Where do feedback widgets usually become the most distracting in your product?
The "sticky score" bit is genuinely clever, way more useful than a noisy spreadsheet of comments. Wish more tools treated feedback like a living product asset instead of a graveyard.
@uuruz0q Exactly. A graveyard tells you what was said. A living product asset tells you what to do next.
Sticky Score is meant to keep the signal alive as the product, customers, and priorities change. What would you want it to weigh most in your workflow: frequency, revenue impact, urgency, or strategic fit?
Love how it captures the surrounding context when you flag something, makes triaging feedback way less painful later. Wish I'd had this during my last sprint.
@evrenmesut52520 That’s exactly the point. Feedback without context is just noise. Genius keeps the moment intact, so when it’s time to act, you’re not guessing what the user meant.
Where did that missing context slow your team down the most?
finally something that doesn't make me dig through slack threads to remember what users actually said. the context capture is pretty clever, basically you drop one widget and forget about it.
@safiyealpak That’s the promise. Feedback shouldn’t become archaeology. Drop in one widget, preserve the moment, and let the signal find its way back to the product. What kind of feedback usually gets buried deepest in your Slack threads: bugs, feature requests, or the little comments that reveal a bigger problem?
@pmdaniels, this is exactly why we built Genius. Not to collect more comments, but to keep a direct line between the people using the product and the people shaping it. I’m glad the Linear handoff is already making that loop useful.
And you’re right about the integrations. A good tool should disappear into the workflow, and the setup should feel just as effortless. We’re tightening that experience into a clearer, guided flow.
Which part of the integration setup created the most friction for you? I want to make sure we fix the moment that actually matters.