3 ms·
Ask HN: What's the current state of the art in flag/report buttons?
Has anyone done in-depth look into flag/report buttons?
I want to make reporting as easy as possible on my platform. I realized that for many people, "flag" may not be understandable, even when the text is in red. I thought maybe using "report" instead, or some kind of icon?
What else is out there? Facebook uses "Get Help", iirc. Reddit's says "report".
My process after pressing the button is much better (no mandatory forms to fill out), but I want the user to know the button is there in the first place.
Also, where is the best place to put it? Top right corner? With all the other actions, at the bottom? Near the title?
Accidental clicks are a much lower concern than under-reporting of problem posts.
- codingdave 6y agoThese sound less like tech questions and more like UX questions. You'll need to ask your end users what labelling makes the most sense to them, and where to put design elements. I don't know that there is a standard answer for all audiences.
- forgotmypw17 6y agoWould you be interested in pretending to be my user for a moment? Imagine that you, a software professional with 25+ years experience, are using a forum. What do you want from flag/report buttons? I guess you would be able to find and use them whether they were at the top or at the bottom, whether they were called report or flag, and whether they required confirmation or not. I've seen some report/downvote buttons which give you a dropdown for the reason right on the page, which is pretty cool. (lobsters) Is there anything you can imagine that a flag button would do that they don't do already? For example, on my site, the report becomes a publicly visible item itself, so you can reply and comment on it, and flag the flag itself, even. Does that sound useful to you, or just one more layer of things to click through?