Notification

The Notification pattern allows users to be informed about events that occur, associated with an application. These events include: new messages, calendar events, data updates, status changes, etc... Notifications is similar to a warning system or news channel, where alerts are broadcast. There are two variations of notifications described in this pattern:

• Outside App Notifications (Native): This includes notifications that flow through the OS. Android and iOS have specific guidelines for handling these. There are two general types of native notifications:
• Local Notification: This is scheduled by an app and delivered by the OS on the same device, regardless of whether the app is currently running in the foreground. For example, a calendar or to-do app can schedule a local notification to alert people of an upcoming meeting or due date.
• Push Notification: This is sent by an app's remote server to the a Push Notification service, which pushes the notification to all devices that have the app installed. For example, a game that a user can play against remote opponents can update all players with the latest move.
• Inside App Notification: This includes notifications that are specific to an application and do not need to flow through the iOS.

Appearance

Appearance characteristics for this pattern.

• Badges: A small badge that appears on top of an icon, right of a list item, or some other location. There are two types of badges:
• Count Badges: The badge could have a number, that indicates the number of pending notifications.
• Status Badges: The badge could have a status icon, that indicates the current status of an item.
• Messages: A short message that is displayed to indicate an update. There are two types of messages:
• Inline Message: A badge or small count bubble that appear with message about the pending notifications.
• Popup Message: A brief message indicating that a notification is pending either for the application or selected page.
• Notification List: This is a list of existing notifications or updates/items that have occurred.
• Animation: Optionally, display an animation on the badge or message when a notification arrives.
• Sound: Allow the user the ability to control whether a sound is played when a new notification is received.

Behavior

Common behaviors for this pattern.

• Duration: Notifications should only appear if they are pending review by the user. The notification badge, message or indicator should disappear if the user has reviewed the notification.
• Dismissing: Notifications can either be time sensitive or be dismissed by users.

Usage

Usage guidelines for this pattern.

• Keep badge contents up to date.
• Do not send multiple notifications for the same event.
• Provide a brief, custom message that does not include your application name, just icon.
• Associate your application icon with the notification message.
• Provide a useful label for the action button in a popup message that needs to be dismissed.
• Use a sound, that users can choose to hear when a notification arrives.
• Navigate to the correction location, when linking from the notification.
• Set and manage the notification priority.
• Allow users notifications to be optional.

Related

• Used On: Phone, Tablet
• Also Called: Push Notification
• Related Components: None
• Related Patterns: Dialog
• Resources: iOS Notifications, Android Notifications