Show HN: Most users won't report bugs unless you make it stupidly easy
bugdrop.appMost feedback tools are built like people actually want to report bugs. They don’t. Unless you make it dead-simple, or better yet — a little fun.
After shipping a few SaaS products, I noticed a pattern: Bugs? Yes. Bug reports? No.
Not because users didn’t care but because reporting bugs is usually a terrible experience.
Most tools want users to:
* Fill out a long form
* Enter their email
* Describe a bug they barely understand
* Maybe sign in or create an account
* Then maybe submit it
Let’s be real: no one’s doing that. Especially not someone just trying to use your product.
So I built Bugdrop. It’s a little draggable bug icon that users can drop right on the issue, type a quick note, and they’re done. No logins. No forms. Just context-rich feedback that your team can actually use — with screenshots, browser info, even console logs if they hit an error.
And weirdly? People actually use it. Even non-technical users click it just because "the little bug looked fun."
I didn’t want to build another "feedback suite". I just wanted something lightweight, fast, and so stupidly simple that people actually report stuff. If you've ever had a user say “something’s broken” and then ghost you forever, you probably get where I’m coming from.
What I’m most proud of? People are actually using it. And their users? They’re actually reporting stuff. Even non-technical ones.
Would love to hear if you’ve faced similar problems, and if this feels like something that would’ve helped in your own projects. Not trying to sell you anything — just sharing something I built to scratch my own itch.
I use an app to get work dome. The app fails disrupting my work. Submitting a bug hijacks my effort from my already failed work, to working for the app developer. The operative term for bug reporting is "submit"! I have to submit to a gauntlet of criteria to justify that the app screwed up when the app maker assumes I've screwed up. If I endure the submission, I'm argued with about whether I know what I'm doing, then if I convince the developer I do, I am dismissed because it's not that important, or more commonly, I am totally ignored. I end up working as a slave for the developer! Of course most don't bother. They're quickly conditioned to ignore bugs and/or to go elsewhere. It's SOP across the industry. And plenty of companies charge you to engage over bugs!
Neat idea! One thing I'd recommend though - on your website, on the landing page, put a short video/animated gif that immediately shows an example of use. Also, it took me quite a while to spot the little bug in the bottom-left corner so you may want to perhaps expose it a little bit more? Perhaps add a little animation that focuses the user's attention there? Good luck!
Thank you! I already have a quick demo video on the landing page, let me know if it's not showing on your end. I'll also be making some changes to the bug icon to help draw more user attention to it.
Great idea. How do I place the bug icon in the location I want (e.g. in a custom header), or use a different icon than the one provided?
Currently, widget customization is somewhat limited. You can only position it on the left or right side, and you're able to change the bug's color (options include red, green, yellow, and a few others) as well as its size. However, I do plan to add more customization options in the future.
Clever. I am going to bring this up in our tech meeting tomorrow as I really like it.
That’s great! Let me know how the meeting goes :)