I have āread on openā toggled off. Meaning the only way it clears from notifications from inbox is if I intentionally tick it off. This helps me if I want to leave it unmarked for further review (itās like a stage one as opposed to the bookmarks which are an even more selective stage 2 for longer-term review)
Once I review a ticket update and swipe back out to notification inbox screen, currently my ocd makes me pay careful attention to āmark readā the appropriate item. I could see value to having a button intra-ticket that:
1) marks the ticket as read
2) automatically backs you back out to inbox
Could also have it on the action bar or the 3 line button as well.
I dig this idea. Not totally sold on the UX of popping back, but at least having a button would be nice. Idk where best to put it:
Sent with GitHawk
Manage floating button would make a lot of sense, but just bear in mind, at least with my permissions as a normal user, I only have that button for my own posts. This would add the button for ALL posts now since every post can essentially be marked read. I kind of dig that, I like the button and it gives it an even greater feeling of consistency.
I can also be a proponent of replacing share. The iOS share button is a button Iāve always vehemently opposed and always prefer app-specific implementations instead. Perhaps Iām biased because I just donāt use it.
Either way I think either one works, just reinforcing some of the affects of either route.
Thereās also a way to add custom buttons to the share sheet that could be used here.
Most helpful comment
Manage floating button would make a lot of sense, but just bear in mind, at least with my permissions as a normal user, I only have that button for my own posts. This would add the button for ALL posts now since every post can essentially be marked read. I kind of dig that, I like the button and it gives it an even greater feeling of consistency.
I can also be a proponent of replacing share. The iOS share button is a button Iāve always vehemently opposed and always prefer app-specific implementations instead. Perhaps Iām biased because I just donāt use it.
Either way I think either one works, just reinforcing some of the affects of either route.