# UX improvements on header dropdown (notifications)

**URL:** https://meta.discourse.org/t/ux-improvements-on-header-dropdown-notifications/370110
**Category:** UX
**Tags:** notifications, interface
**Created:** [June 13, 2025, 6:05pm UTC](https://meta.discourse.org/t/ux-improvements-on-header-dropdown-notifications/370110 "2025-06-13T18:05:01Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [June 13, 2025, 6:05pm UTC](https://meta.discourse.org/t/ux-improvements-on-header-dropdown-notifications/370110/1 "2025-06-13T18:05:01Z")

</div>

> _Continuing the discussion from [New header dropdown / notification menu styles](https://meta.discourse.org/t/new-header-dropdown-notification-menu-styles/369574/40):_

While I appreciate the recent visual improvements to the notification stylesheet, I believe we need to address some fundamental UX issues that impact both new and existing users.

The current system has several redundant navigation elements that create confusion.

We have **All notifications** and **Other notifications** serving similar functions, **Messages** and **Chats** with three separate entry points for messaging (menu item, chat bubble icon, and header link) all within the same interface section.

And **Avatar** versus **Profile** plus **Summary** (and **Preferences** ) where activities and summary are housed _inside_ the profile while notifications remain _outside_, creating inconsistent mental models.

The iconography also assumes familiarity with Discourse conventions:

 ![Screenshot_-11](https://global.discourse-cdn.com/meta/original/4X/1/1/b/11b7476517ca8477d874d2ead221120f1605de5e.png)

For new users, repeated icons lack intuitive meaning, creating barriers to adoption and increasing cognitive load during initial platform exploration.

I kindly think getting third-party UX consultation would be beneficial for this evaluation because as daily Discourse users, we’ve developed learned behaviors that mask genuine usability pain points.

_Fresh eyes can identify friction that we’ve unconsciously adapted to—friction that newcomers experience as genuine barriers to meaningful platform engagement._

What are your thoughts on how to approach improving these interface elements?

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [June 13, 2025, 6:59pm UTC](https://meta.discourse.org/t/ux-improvements-on-header-dropdown-notifications/370110/2 "2025-06-13T18:59:43Z")

</div>

> [@satonotdead](#):
>
> **All notifications** and **Other notifications** serving similar functions

These aren’t really similar, though it may be unclear depending on the types of notifications you current have. “All notifications” is a combination of all the different notification types — it’s the primary notification feed.

“Other notifications” is for certain types of notifications that don’t fit into other filters (things like badges, edits, links, solutions).

Of course, the fact that you didn’t know that isn’t your fault and may be something we can work on clarifying.

> [@satonotdead](#):
>
> **Messages** and **Chats** with three separate entry points for messaging (menu item, chat bubble icon, and header link)

Yeah we have some ideas for how to unify the navigation a little bit, hopefully we can get to them soon. I think messages and direct chats are a little redundant, but we have a lot of functionality tied to messages (email inboxes, moderation) and chat is optional… so we’re going to have both for the foreseeable future.

> [@satonotdead](#):
>
> For new users, repeated icons lack intuitive meaning

fortunately this is an easy one, the icons will all be unique after this is merged [UX: make all preference icons unique by awesomerobot · Pull Request #33202 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/33202)

Thanks for the feedback!
