I'm curious, are you using the “pin user” or “bury user” feature more on fevela.me? Or are you not interested in either of them?
I'm a bury maxi.
Discussion
Bury user. I would like an option to mark as read.
Mark as read the single user? Everything?
The single user, sometimes I've read it to another customer. It would also be interesting that users already read were hidden and only returned to the top when publishing another note.
*Client, no custumer 😅
To mark a single user as read you just need to click the counter; probably any other way (e.g. using a menu action) would require 2 clicks, so it seem a better solution.
Instead I'm thinking about an action to mark an user as *unread*, since sometime you click it but you don't have the actual time to read everything.
About the hiding feature, you are not the first that asked it, I'm evaluating it.
I think of "pin" as a semi-permanent action, and 'bury' as semi-temporary. I like them both, but bury gets used more because of the nature of annoyance.
About to try fevela for the first time. I'll let you know after a while
both.
only issue with the feature is that if you're at the bottom and you want to "pin" someone, you get scrolled all the way back to the top. ditto/opposite for "bury".
Well, the best UX here is quite subjective, seeing the result of the action (with the scrolling) VS letting the user go on an pick other profiles. I need to evaluate.
For sure I dislike the fact that when you unpin/unbury someone, the scrolling follow the profile, this makes no sense, I need to fix it.
a "sent to top" toast could do it.
users get past the 'feature learning' phase pretty quick and enter 'efficiency from here on out' permanently.
I don't like when an application is too verbose about what it is doing during the interaction, it usually is a red flag about usability. Then toasts notifications opens a lot UX issue (how to stack them, auto-close o explicit button, etc).
Maybe the row could simply change is aspect and present the "sent to top" info.
Anyway, as you mentioned later, users should quickly learn how it works, and after a while they will no longer pay much attention to these details.