Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark all notifications as read #31

Open
jhass opened this issue Nov 16, 2020 · 3 comments
Open

Mark all notifications as read #31

jhass opened this issue Nov 16, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@jhass
Copy link
Owner

jhass commented Nov 16, 2020

Extracted from #18

There should be a feature to mark all unread notifications as read.

Any UI suggestions? I can't really come up with something that does not feel like it either wastes space or leads to jumpy UI.

@jhass jhass added the enhancement New feature or request label Nov 16, 2020
@tclaus
Copy link
Collaborator

tclaus commented Nov 17, 2020

After some investigation it turns out two possible solutions:

  1. Keep it, as it is
  2. Remove badge after open the tab
  3. "Mark all as read"

My ideas:

  1. The count of unread items may rise over time - User is urged to make housekeeping every day by opening each item. (Which is annoying the second day)

  2. I found this on many other apps - the Badge disappears after opening the Tab, but the unread item still has a different background color than read items. User still 'sees' unread items, but is not urged (by the red badge) to open each one. User can just 'forget' older items.

  3. Uncommon, has a new UI-Element. Can be solved gracefully by 2)

So what do you thing about solution 2) ?

@jhass
Copy link
Owner Author

jhass commented Nov 19, 2020

The 2. is tricky due to two things:

  1. Cross-client consistency. The web interface currently does not work this way, so we would have different criteria for when to show the red bubble. Also any new competing client could choose to follow the web interface behavior.
  2. Diaspora recycles unread notifications. Say you got a "comment on your post" notification. While it's unread the existing notification is updated as additional comments arrive. But after the notification was marked as read, the next comment triggers a new notification.

    I doubt there's a reliable way to detect an already "seen" notification was updated/recycled by Diaspora and should be resurfaced to the user.

@tclaus
Copy link
Collaborator

tclaus commented Nov 19, 2020

From user perspective this should be no brainier.
If the backend recycles messages - ok. Not 100% perfect in an app, (that's a change on an old notification). It might be sufficient if "new" ones are detected and marked with a badge.
Simply remember a time stamp from last open the tab and count all notifications since then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants