111–120 of 226 posts
Earlier quoted context omitted.
Transparency in the form of a public ticket tracker would solve that.
Apple doesn't have this. They're super successful. I hate it! But, clearly that's not an argument most bean counters are going to care about given such successful companies have some of the worst feedback mechanisms.
Earlier quoted context omitted.
Apple doesn't have this. They're super successful. I hate it! But, clearly that's not an argument most bean counters are going to care about given such successful companies have some of the worst feedback mechanisms.
They are not super successful at fixing bugs.
I love the UI concept. Being able to point at a broken thing rather than try to uniquely describe the position/state/path to a broken thing is smart! Hooooever, "bug" could be a bit ambiguous to a lot of people. Looks like in a real deployment, you have a little tooltip that says "Spotted a bug? Drag me there!". That makes sense to developers and the like... but those are also the sorts of people most likely to write…
Congrats on shipping! Here's some quick feedback -- hope it's useful: 1. Is the little bug icon sufficiently visible? I'm not sure... 2. Do visitors automatically know what to do with the bug? You have a tooltip, but do all visitors know what "Spotted a bug?" means? 3. [more of a suggestion; perhaps it does this already] Would be great if the bug position pulled in a CSS class or the content surrounding the "dropped"…
2) I'm considering updating the popup text to something more approachable, like "Something’s not working?" or "Spot a problem?"
3) Currently, it doesn't send class names—but that's a great suggestion. Thank you!
I love this. Especially the sane pricing. Only thing I would add is after submit it should allow you to enter an email address or something so that (a) the user can get updates on the progress of fixes; and (b) be contacted if the dev needs more info.
I use to report bugs all the time with details of the bug and what I was doing and if possible how to cause it. But then when you encounter the same bugs years later doing some very common task that you momentarily forgot to do your work around for, it made me wonder why I was wasting my time reporting it. These days I rarely report bugs unless it is brand new software released a few weeks ago at most, or a brand new…
I think I've reported bugs to Bloomz (the awful communication app my school uses), jpmonette/feed (the node/typescript RSS feed generation library), and I think at one point I reported one to Newsblur, and they all got fixed.
This sounds neat! Do you have a site that describes how it's added to an existing project?
Bugdrop won't work for most users, since they don't real tooltips. 1. I load https://bugdrop.app/ 2. The site days 'try bugdrop' and points to the left bottom corner. 3. I click the bug. Nothing happens. On further inspection, there is sometimes a tooltip that tells me clicking won't work and I need to drag the bug over the part of the UI that failed, but I didn't read that when I first used it and I won't use it a s…
There's the other side of the coin of reporting bugs besides initial friction: if the user feels like the bug reports end up in a black hole, then they will disincentivized from doing so. What happens after the user files a bug from their point of view? Is there a follow-up, or is it like throwing a message in a bottle?
Why not a video snippet? Why a note?