Suggestion for notification circle color (change to red if contains new order notification)

[dsmurrell]

I get a lot of notifications (mostly follow notifications). This causes me to miss the most important notifications (new orders). Would it be possible to change the color of the notification circle (top left with the number in it) to red if it contains at least 1 new order notification?

Ran this suggestion by DrWasho who liked it. Adding it here in case he's forgotten about it.

[morebrownies]

We've discussed giving more control over notifications e.g. turning certain types off. That may alleviate some of the problem, but we may also want to consider grouping notifications types into sections within the notification tray. That would enable you to quickly see latest orders, followers, comments, etc nicely grouped into sections instead of having to scroll through one general list.

[dsmurrell]

@morebrownies even better.

[morebrownies]

Here's a comp of what I'm thinking

[rmisio]

(thinking out loud)

Assuming you want to allow lazy loading on new tabs, paginating presents a lot of interesting challenges to making this happen.

Option A: As of now, the get_notifications API doesn't allow us to fetch notifications by particular type. When they lazy load scroll on one of the other tabs (e.g. Orders), we could just fetch the next page of "all" notifications and put the results in the All tab and then if any are for Orders, put those in the Orders tab.

This has some downsides: 1.) Inconsistent page sizes. After one scroll, only 3 of the returned notifications may be for order, whereas after another scroll 6 of them may be for orders. 2.) Similarly, it's possible none of the notifications returned are for order, in which case the user would see a spinner and when it goes away, no new notifications are displayed. This could happen a number of times in a row. Also, there may be no notifications left for order in any of the remaining pages, but the client has no way of knowing this. So, the user would just keep getting the spinner when they scrolled down.

Option B: Another option is having the server update the API so that we can request notifications by type. Then each tab would only get their specific notifications from the server and we could make it so any fetched into the All tab are also appropriately duplicated into the other tabs.

Option C: A third option, is just to only allow lazy loading on the All tab, in which case the All tab will be populated with the resulting page of notifications and any that match the filters will also be duplicated in their respective filter tabs. But, scrolling down on the other tabs would never load any more notifications. Would that work from a UX perspective?

[jjeffryes]

I think the best option would be to update the API to return notifications by type. @cpacia any thoughts?