Electricity usage - depends why it's being monitored
* Used to be hung-up on this. But now I've decided that it's all about context and keeping things relevant.
* If you receive the data and it's still relevant and usable then the delivery time is good enough.
* e.g. a tweet 10 seconds after it's been posted
* site analytics 10 seconds after a user comes online
* Sometimes it's got to be instant:
* stock quotes
* game moves
* alert notifications
* break response in a car
What is the realtime web?
Immediate availability of data - Twitter/Social Media
Instant delivery of data
Publish & Subscribe (PubSub)
Truly interactive web apps - We used to call these RIAs
Improved User Experience
& User Engagement
* The immediate availability of data
* Searchable, discoverable, data available must faster than we'd seen before
* The instant delivery of data
* A search isn't just a one-off thing any more. You are registering your interest in something you are making a subscription.
* Events signify something has just happened. New data is available.
* Technology to achieve this has been around for ages, but it's just gone mainstream.
* Pub/Sub to the masses
* With this technology we can now offer/build:
* Realtime data - financial data, sports data, betting odds, where instant updates matter
* Notifications: New tweets, facebook status updates, calendar appointment prompts, users coming online prompt
* Customer support chat, user to user chat (facebook chat)
* Collaboration: Google Draw, Docs, Spreadsheets
* Social media reaction/integration: Tweets, Facebook likes, Blog post notifications, Images from TwitPic or yFrog/ImageShack
* Games - whether simple gamification updates or true realtime html5 multiplayer games
* All of these can be used to improve the UX and UE
* UX/UE improvements
* We are constantly trying to improve web applications:
* HTML
* CSS
* JavaScript
* realtime communication