Re:GitHub's new notifications: a case of regressive design
by timdorr on Friday March 13, 2020 @12:22PM
(#22568549)
> Additionally, clicking on "Done" once you're in the notification-specific page will navigate you away from the current page back to the notifications list. This is pretty disruptive to me.
But if you're done with that notification, why would you want to stick around? You wouldn't yet be done by definition.
Re:GitHub's new notifications: a case of regressive design
by eatonphil on Friday March 13, 2020 @12:25PM
(#22568574)
I guess that's just not how I think or how I'm used to using an inbox. I click done to get the banner out of my face. The important part was the notification not the requirement to buy into their task management system.
Additionally, clicking on "Done" once you're in the notification-specific page will navigate you away from the current page back to the notifications list. This is pretty disruptive to me.
Granted, I keep inbox 0 everywhere so my habits may be different than average.
I like that the notifications are removed in realtime from the list if you click "Read" there. (However, possibly due to varying line lengths, the page sometimes jumps while marking each item as read in the list. This is annoying.)
My guess is that the product team had a solid UX in mind but the engineering team was pushed to release before it was polished enough to be a solid improvement on the existing system.