Hand the mic to your users and testers

Sure, we all collect input from users before development. And work the issues from our testers during. But what about after? Why do we turn off the mic and plug our ears after deployment? It's astonishing to me how many web apps don't have a built-in way to collect feedback and report issues. But I sympathize with product team. Most of the feedback and issue widgets out there want to lock you into a subscription and their own issue management system. Like many other teams, though, we have GitHub for that. So we built an ultra-light, framework-agnostic widget and GitHub connector. Now our users and testers can stay in the app, our developers can work in GitHub, and the two ends are connected. Nice. This seems like something that would be useful to others, so we made it open source and published the connector as a GitHub App . Give it a try! Naturally, you can give your feedback and report issues from the widget on our GitHub Pages . Handing you the mic...