Mobile IxD

The frequency with which to notify the user must be appropriate to the significance of the notification, the content contained within the notification, and the current usage context. Error dialogs, new message alerts, sports scores, stock price changes and calendar reminders are just some examples of notifications.

Factor the user’s current activity into the decision of whether to trigger a notification or wait
If possible, also factor in the user’s historical activity and allow the user to shape the notification experience in real-time through simple actions (e.g., if a type of notification is always quickly acknowledged, consider notifying more frequently)
Always notify for critical errors and those in which there may be loss of user data – less important errors that do not prevent the user from working can be delayed until a time when they are not as intrusive
Always notify for scheduling and task reminders set by the user
Unless there is significant doubt as to an action’s effectiveness for very specific reasons, avoid notifications for positive results of an action (e.g. after a message is sent successfully)
Allow a basic level of manual configuration of notification frequency, minimally always/never
Notifications should be transient (except critical errors) such that the user can resume their previous activity prior to the notification triggering

dave@mobileixd.com