new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

IBM Carbon · all subjects

notification/design-considerations

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Notification priority and visual style

Notifications range in their priority and therefore should vary in their disruptiveness to users. Carbon offers two visual styles for inline and toast notifications. The high-contrast style is more visually disruptive and should be used for notifications that are urgent or critical. The low-contrast style is better for supplemental messaging or other low priority use cases. You should never mix styles within the variations.

Optional vs required notification actions

Optional action notifications can include a ghost or tertiary button that lets users interact with them, but taking action should be optional and should not block the user from continuing with their current task. Required action notifications must block users from dismissing the notification or continuing with their task until the message has been addressed. Required action notifications should only be used when it is critical the user sees the notification or the user needs to take action right away.

Give your agent this brain