
BugDrop
In-app feedback that creates GitHub Issues with screenshots
125 followers
In-app feedback that creates GitHub Issues with screenshots
125 followers
Free, open source website feedback widget. Users report bugs with screenshots and annotations; issues are created in GitHub automatically. One script tag, zero config, fully customizable to match any app.









meme search
How does it handle spam or duplicate reports? if five users report the same bug, is there a way to triage them before they hit the repo, or does it just create five separate issues? either way, the demo looks very smooth. @neonwatty
meme search
@priya_kushwaha1 Great question! At present each feedback drops as a distinct issue. I could certainly see adding a call to Claude / Codex wired in on every X feedback submissions to tidy up / consolidate BugDrop issues being a future feature (I essentially do this to triage issues locally today). A solid option for those wanting issue consolidation.
Screenshots from real users will inevitably capture sensitive data (passwords, emails, customer info). Curious if BugDrop has any masking or blur options before the screenshot leaves the user's browser.
meme search
@ebazan33 BugDrop supports two redaction modes today.
Developer-configured: developers can mark sensitive page elements with data-bugdrop-mask, and BugDrop automatically covers those regions in the captured screenshot before the user submits. A custom example looks like:
There are also some defaults setup beyond this built in (e.g., passwords / credit-card inputs / etc.,) that are masked automatically.
User-controlled: users can review a screenshot before submitting feedback and drag black redaction boxes over anything else they want to hide. Both modes happen in the browser, so the server only receives the final already-masked/redacted PNG.
Here's a short gif of the user-side redaction in the current UX.
@neonwatty Thorough setup. Curious how often users actually drag the redaction boxes vs just trusting the defaults. The friction question is usually what kills user-controlled privacy features.
meme search
@ebazan33 Great feedback: makes me think that some improved UX / messaging for users - when screenshotting an area with already (developer-redacted) fields to help them understand what will be auto-redacted - is in order.
@neonwatty That'd land. A simple "X fields auto-masked" indicator near the redact button would probably be enough. Gives users confidence without making them scan everything. Good luck.
This solves a real pain translating user feedback into actionable issues is where a lot of reports go to die. Does it work with mobile apps or is it web-only right now?
meme search
@imad_elkhafi web / wrapped mobile apps only for now.
@neonwatty Makes sense as a starting point native mobile SDK support would be a great next step when you get there.
one script tag + github marketplace app is all it takes. this is how feedback should work
meme search
@edan_tusi agreed 😎!