497
edits
Notifications: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
|Feature users and use cases=Lots of use cases, but here are some examples of incoming messages from: | |Feature users and use cases=Lots of use cases, but here are some examples of incoming messages from: | ||
Pulse/bounce/glow | |||
*real time chat | |||
*asynchronous (but important) direct messages through social networks | |||
Badging is a non-goal. The increasing size of the badge creates a game mechanic where users must get the number down to zero, which isn't a good pattern, and ultimately makes them feel like they are failing. | Ambient | ||
*asynchronous email | |||
*asynchronous (and not important) messages through social networks | |||
*various random niche sites that need to notify you of events | |||
|Feature non-goals=*Interrupt the user's cognitive flow with notifications that are not relevant or important (the growl effect) | |||
*[b]Badging is a non-goal[/b]. The increasing size of the badge creates a game mechanic where users must get the number down to zero, which isn't a good pattern, and ultimately makes them feel like they are failing. | |||
*Panel notifications need to be user opt in, because they are so destructive to the user's attention and cognitive flow. | |||
|Feature functional spec=Two different API calls: | |Feature functional spec=Two different API calls: | ||
1) Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it) | 1) Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it) | ||