[DONE] Notifications > Reduce noise of read notifications

When viewing notifications it is hard to know which ones have been read and which haven’t.

:man_shrugging: Example

There is a tiny blue dot :large_blue_circle:, which oddly doesn’t match the colour of the dot in the left hand bar.

I suggest two solutions:

  1. User clicks on :gear: and can select Clear read notifications

  2. Read notifications are reduced in prominence (and prominence increases on hover/focus)

Another way to handle this is to have an “Inbox” tab where all new notifications appear, and you must manually “Archive” or clear them after they are read, after which they move to an “Archive” tab.

I like this model because it allows me to easily decide which notifications should continue to appear in my “Inbox”, where they stay on my radar – like a quick list of “things that need my attention”.

Asana also works this way.

5 Likes

I have also been receiving requests for “archiving” and/or “clearing” of individual notifications to reduce the notification clutter of notifications that have been read, similar as described by @Matt_Blais.

2 Likes

Related:

Today I showed our new fibery set-up to my team. Collective feedback: Notifications should disappear after they’ve been read.

Main pain points:

  • Bad overview
  • Noisy, makes you stressed to look at the notifications, even if all of them have been “read”
  • There’s no feeling of “satisfaction” after the notification has been marked as “read”, because nothing happens (well…only the small dot disappears)

Suggestion:
Archive “read” notifications

For example: Notification Inbox + Notification Archive, which is accessible via toggle on top or “load archive” at the bottom

That would help a lot and give people the “zero inbox” happy feeling :slight_smile:

3 Likes

Agree! Notifications in Fibery are also a big frustrations that our team has. It ruines your productivity :sweat_smile:

2 Likes

Notifications is one of the WORST area of Fibery. We know that and do have plans to make it great.

6 Likes

This problem should be solved in the last release