Notifications: Difference between revisions

Jump to navigation Jump to search
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
Ping/Pulse/Bounce
*real time chat
*real time chat
*asynchronous (but important) direct messages through social networks
*asynchronous (but important) direct messages through social networks
Line 26: Line 26:
*Panel notifications need to be user opt in, because they are so destructive to the user's attention and cognitive flow.
*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)
#Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it)
2) Ping (for direct messages, real time chat, etc.  The message captures your attention and continues to bounce, pulse, glow until you interact with it)
#Ping (for direct messages, real time chat, etc.  The message captures your attention and continues to bounce, pulse, glow until you interact with it)
|Feature ux design=http://people.mozilla.com/~faaborg/files/projects/notifications/desktop%20notifications%20i1.png
|Feature ux design=http://people.mozilla.com/~faaborg/files/projects/notifications/desktop%20notifications%20i1.png
}}
}}
497

edits

Navigation menu