2. Why it’s different
• Email is multiple unicast (many copies of single
messages)
• Wave is multicast (single copy of message, many
subscribers)
• For the geeks it’s a publish and subscribe model
with a message queue in the background
3. Anatomy of a Wave
• Waves have wavelets
• Wavelets have blips
4. What can you do with a Wave
• Developers
• Make Robots
• Embed Waves
• Build Gadgets
5. Robots
• COOL!
• Can inspect data within wave
• Can then go do something with it
• Can change content within wave
• For the geeks it’s powered by webhooks
6. Embed Waves
• Waves can go anywhere
• Can insert wave into any HTML file
• Can be inserted in multiple places
• Changes immediately propagated to every
embedded wave
7. Gadgets
• Extending functionality
• XML based Google Gadgets
• Store data within Wave
• Changes can be replayed and are stored on a per
user/wavelet basis
8. What can you do with a Wave
• Users
• Add Robots
• Interact with Gadgets
• Add media (text, images, audio, video)
