Difference between revisions of "KDE Visual Design Group/HIG/Notifications"

(Undo revision 80212 by Agateau (talk))
m (16 revisions imported)
 
(8 intermediate revisions by 3 users not shown)
Line 2: Line 2:
  
 
== Purpose ==
 
== Purpose ==
A ''notification'' is an information that is not directly relevant to the user's current task. It is displayed via a certain [[KDE_Visual_Design_Group/HIG/NotificationMechanism|notification mechanism]] on a panel above/below the taskbar notification area. Notifications inform users about non-critical problems, but they don't prevent them.
+
A ''notification'' is an information that is not directly relevant to the user's current task. It is displayed via a certain notification mechanism on a panel above/below the taskbar notification area. Notifications inform users about non-critical problems, but they don't prevent them.
  
Notifications pop up and overlay all other windows. Multiple notifications are stacked vertically. Notifications disappear after a short period automatically (unless the cursor hovers over them), but can be closed by the user at any point. Each notification has its own [[KDE_Visual_Design_Group/HIG/CentralConfiguration|central configuration]] which can be reached by a button next to the close button.
 
 
== Examples ==
 
== Examples ==
(remark: pictures only?)
+
 
=== Positive ===
 
* Email received
 
* New update available
 
* Download completed
 
* Low battery power
 
todo: picture
 
=== Negative ===
 
* Low space on medium (this information becomes relevant for file managers and invoked as modal message in this case)
 
todo: picture
 
 
== Guidelines ==
 
== Guidelines ==
* Do not use notifications for user assistance (consider to use [[KDE_Visual_Design_Group/HIG/Tooltip|tool-tips]] or [[KDE_Visual_Design_Group/HIG/Balloon|balloons]] for short information, or refer to [[KDE_Visual_Design_Group/HIG/HelpSystem|help system]] for extended text.
+
=== Is this the right control ===
* Do not use notifications for context relevant information that might interfere with the actual workflow (consider to use a [[KDE_Visual_Design_Group/HIG/MessageDialog|message dialog]].
+
* Use a notification to inform about a non-critical problem that is not directly relevant to the user's current task.
* Do not add controls to notification.
+
* Do not use notifications for user assistance (consider to use [[KDE_Visual_Design_Group/HIG/Tooltip|tool-tips]] for short information, or refer to [[KDE_Visual_Design_Group/HIG/HelpSystem|help system]] for extended text).
* Do not override system settings.
+
* Do not use notifications for context relevant information that might interfere with the actual workflow (consider to use a [[KDE_Visual_Design_Group/HIG/Messages|message dialog]]).
* Provide title and content text
+
 
* Make sure to make the origin of the notification clear from the notification title. For instance: "Amarok: Now playing" or "Konsole: Event"
+
=== Behavior ===
 +
* Notifications disappear automatically after a short period (unless the cursor hovers over them), but can be closed by the user at any point (KNotification::NotificationFlag == CloseOnTimeout).
 +
* Do not add more than three actions to a particular notification. And take care about limited space for labels. For instance, ''Skip'', ''Info'', and ''Buy'' in case of Amarok's "Now playing" notification.
 +
 
 +
=== Appearance ===
 +
* Make sure to make the origin of the notification clear from the notification title. For instance: "Amarok: Now playing" or "Konsole: Event".
 
* Keep the notification content concise (no more than about three simple sentences).
 
* Keep the notification content concise (no more than about three simple sentences).
* Customize notification with the origin's icon.
+
* Provide actionable information (e.g. "Low battery power: Approximately 13 min (2%) capacity remaining.").
* Provide actionable information (e.g. "Low battery power" "Only 13 min (2%) capacity remaining. Please save your stuff now. Your system will get shut down soon.")
+
 
 +
== Implementation ==
  
== Code snippets ==
+
[[Category:Usability]][[Category:Behavior]][[Category:User_Assistance]][[Category:User-driven_assistance]]
to be done
 

Latest revision as of 12:21, 30 March 2016


Purpose

A notification is an information that is not directly relevant to the user's current task. It is displayed via a certain notification mechanism on a panel above/below the taskbar notification area. Notifications inform users about non-critical problems, but they don't prevent them.

Examples

Guidelines

Is this the right control

  • Use a notification to inform about a non-critical problem that is not directly relevant to the user's current task.
  • Do not use notifications for user assistance (consider to use tool-tips for short information, or refer to help system for extended text).
  • Do not use notifications for context relevant information that might interfere with the actual workflow (consider to use a message dialog).

Behavior

  • Notifications disappear automatically after a short period (unless the cursor hovers over them), but can be closed by the user at any point (KNotification::NotificationFlag == CloseOnTimeout).
  • Do not add more than three actions to a particular notification. And take care about limited space for labels. For instance, Skip, Info, and Buy in case of Amarok's "Now playing" notification.

Appearance

  • Make sure to make the origin of the notification clear from the notification title. For instance: "Amarok: Now playing" or "Konsole: Event".
  • Keep the notification content concise (no more than about three simple sentences).
  • Provide actionable information (e.g. "Low battery power: Approximately 13 min (2%) capacity remaining.").

Implementation


This page was last edited on 30 March 2016, at 12:21. Content is available under Creative Commons License SA 4.0 unless otherwise noted.