Page MenuHomePhabricator

Investigate if the same bell icon being used for multiple different subscribe/notify actions is an issue.
Open, HighPublic

Description

Background/Goal

As part of the the work described in T427228, the subscribe feature on talk pages will be moved to the article nav bar. Because of its more prominent position now users will be seeing a few bell icons placed more closely together - 1) notification centre on header. 2) subscribe on talk page nav 3) subscribe to specific discussion on talk page. This ticket is an investigation task to see if we need to do any work to clarify it or if its not needed.

User story

As a designer, I want to understand whether users can correctly interpret the different meanings of the same bell icon when it appears in different contexts across the product.

UX considerations and assumptions

  • the icons refer to the same thing: notifications, so using the same icon seems fair
  • across other platforms the bell icon is widely used for both "notification counter" and "subscribe"
  • both actions are non-destructive, low risk and easy to reverse, if the user gets it wrong, it's not a big deal
  • we are already doing this, they just haven't been this close together before

Acceptance criteria (or Done)

Event Timeline

@Sneha can you provide any screenshot examples of how you were initially envisioning using the bell icon in multiple places?

DTorsani-WMF moved this task from Backlog to In Progress on the Codex board.

After some research, here are my initial findings:

  • Overall, the assumptions here are correct—the bell icon refers to the same idea and cognitively should be perceived correctly, based on context, other apps do use the concepts of subscribing and notifications together, these actions are reversible so it's not a big deal.
  • The main concern here would be the law of proximity, especially on mobile where the labels are dropping and you have the same icon relatively close to one another.
  • A general finding from Neilson Norman Group is that digital icons get misinterpreted more commonly than we would like to think. This is why we should use icons as decorative elements which ideally accompany a label. That being said, the bell icon and the concept of subscribing and notifications is a very common and familiar one, so I'm not sure there would really be problems with this.
  • YouTube for example, uses a bell icon for global notifications in the top header, while it explicitly spells out "subscribe" on videos. Slack, on the other hand, uses a bell icon to represent "Activity" as well "muting", and in the same overall interface. On the desktop app, you'll see these icons represented in various ways in the same interface, but not without either a label or tooltip explaining the action. On the mobile app, you won't necessarily find the bell icon representing various actions in the same interface.

My general recommendation would be that it is OK to use the bell icon to represent notifications in the header and subscribing to something within a page. I would suggest using a label wherever possible, particularly for subscribe, as that's a slightly less familiar action than a global notification bell. On mobile, where space is limited, consider where the two bells are located on the same page, or where something could be within a menu and ideally with a label. It is certainly worth learning from users either during a user test beforehand or from usage data afterwards to determine if there is any confusion and generally how these two concepts are translating through the bell icon.