1 / 56

Google Wave

Google Wave. John Raynor – Business Research Services High Point Public Library Mark Sanders – Head of Reference East Carolina University. Why Google Wave?. Email’s Limitations. Email was invented in 1971. Why Google Wave?. Email’s Limitations. Email was invented in 1971.

skip
Download Presentation

Google Wave

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Google Wave John Raynor – Business Research Services High Point Public Library Mark Sanders – Head of Reference East Carolina University

  2. Why Google Wave? Email’s Limitations Email was invented in 1971.

  3. Why Google Wave? Email’s Limitations Email was invented in 1971. Before HTML, the browser, and the World-Wide Web

  4. Why Google Wave? Email’s Limitations Email was invented in 1971. Before HTML, the browser, and the World-Wide Web Before the graphic user interface

  5. Why Google Wave? Email’s Limitations Email was invented in 1971. Before the HTML, the browser, and the World-Wide Web Before the graphic user interface Before the personal computer An Apple I computer in its hand-made case, circa 1976

  6. Why Google Wave? Email’s Limitations In September of 1971, ARPANET (the Internet’s precursor) had only 18 nodes

  7. Why Google Wave? Email’s Limitations In September of 1971, ARPANET (the Internet’s precursor) had only 18 nodes The DEC PDP-10s at BBN Technologies of Cambridge, Massachusetts which sent, and received, the first ARPANET email with an “@” sign (from Ray Tomlinson’s personal web page)

  8. Why Google Wave? Email’s Limitations In September of 1971, ARPANET (the Internet’s precursor) had only 18 nodes The DEC PDP-10s at BBN Technologies of Cambridge, Massachusetts which sent, and received, the first ARPANET email with an “@” sign (from Ray Tomlinson’s personal web page)

  9. Why Google Wave? Email’s Limitations To its credit, email hasn’t fallen completely behind the times, but its ability to display content is still seriously limited.

  10. Why Google Wave? Email’s Limitations To its credit, email hasn’t fallen completely behind the times

  11. Why Google Wave? Email’s Limitations To its credit, email hasn’t fallen completely behind the times, but its ability to display content is still seriously limited. Images are relegated to the end of the message, as “attachments,” and viewing them often involves extra steps.

  12. Why Google Wave? Email’s Limitations To its credit, email hasn’t fallen completely behind the times, but its ability to display content is still seriously limited. Email can’t, moreover, display “live” content from the Internet – it can only provide links to it.

  13. Why Google Wave? Email’s Limitations Traditional email is simply the electronic equivalent of the old-fashioned paper memo

  14. Why Google Wave? Email’s Limitations You send an email message, and the recipient gets a copy… …which is as inert, and as immutable, as a paper memo in a filing cabinet.

  15. Why Google Wave? Email’s Limitations Email’s other problems: Original messages are appended to the ends of replies. Replying to one specific part of an email message involves cutting-and-pasting quoted passages, and inserting new text between them. It’s hard to add new participants to an email-based conversation and bring them “up to speed.” Likewise, replying to some, but not all, of the people in an email-based conversation involves sending duplicate messages with edited recipient lists.

  16. Why Google Wave? Email Re-Invented So what, then, is a wave?

  17. Why Google Wave? Email Re-Invented So what, then, is a wave? A wave is notjust another kind of message!

  18. Why Google Wave? Email Re-Invented So what, then, is a wave? A wave is notjust another kind of message! A wave is a semi-permanent online space in which two or more users can interact and create content together.

  19. Why Google Wave? Email Re-Invented Email is like… sending memos back and forth

  20. Why Google Wave? Email Re-Invented Email is like… Google Wave is like… sending memos back and forth sharing a conference room with your collaborators

  21. Why Google Wave? Email Re-Invented Google Wave shares some features with other kinds of online communication/collaboration: Wikis and Google Docs: Multiple author documents with revision control

  22. Why Google Wave? Email Re-Invented Google Wave shares some features with other kinds of online communication/collaboration: Wikis and Google Docs: Multiple author documents with revision control Instant Messaging: You can see who’s logged in, and work together in real-time

  23. Why Google Wave? Email Re-Invented Google Wave shares some features with other kinds of online communication/collaboration: Wikis and Google Docs: Multiple author documents with revision control Instant Messaging: You can see who’s logged in, and work together in real-time Online Forums: “Threaded” conversations

  24. A Brief History of Wave • Developed by brothers Lars and Jens Rasmussen in Sydney, Australia circa 2004-2007 • Announced by Google May 2009 • Preview released to 100,000 developers in September 2009 • Released to the general public in May 2010 • August 2010 - discontinue new standalone Wave development

  25. Basic Wave functionality Let’s Look at a Wave

  26. Basic Wave functionality Running conversations both public (group) and private (individual)

  27. Basic Wave functionality Running conversations both public (group) and private (individual)

  28. Basic Wave functionality Embedded videos

  29. Basic Wave functionality Embedded web pages

  30. Basic Wave functionality Attached files

  31. Basic Wave functionality Photo slideshow

  32. Extensions Gadgets – Maps

  33. Extensions Gadgets – Yes/No/Maybe

  34. Extensions Extensions – Polls

  35. Extensions Robots

  36. Extensions Extensions – Games

  37. Why Google Wave? Google Wave’s Strengths Sharing lots of information with a team and quickly making decisions

  38. Why Google Wave? Google Wave’s Strengths Communication which involves sharing images and files

  39. Why Google Wave? Google Wave’s Strengths Developing content collaboratively Writing the Declaration of Independence as a Google Wave demonstration

  40. Why Google Wave? Google Wave’s Strengths Developing content collaboratively An important caveat: Google Wave is good for working out what you want to say, but is not good for creating polished documents! Wave’s formatting and document-export capabilities are limited.

  41. Why Google Wave? Google Wave in Practice Google Wave is not an “all-purpose communication tool”

  42. Why Google Wave? Google Wave in Practice Google Wave is not an “all-purpose communication tool” • The USF Tampa Library’s Experience with Wave • Wave was used by the library’s website-redesign team • Many issues converged before the site could “go live” • Decisions had to be made quickly – it was “crunch time” • Information had to be shared with the whole team

  43. Why Google Wave? Google Wave in Practice Google Wave is not an “all-purpose communication tool” • The USF Tampa Library’s Experience with Wave • Unfortunately… • Weekly team meetings were no longer enough • Subsets of the team were sharing information by email, • but not everyone was staying “in the loop,” all the time.

  44. Why Google Wave? Google Wave in Practice Google Wave is not an “all-purpose communication tool” The USF Tampa Library’s Experience with Wave The new website “went live” in mid-December of 2009. The library hasn’t used Google Wave since then.

  45. Why Google Wave? Wave’s Limitations A wave should not be regarded as a “permanent” product

  46. Why Google Wave? Wave’s Limitations A wave should not be regarded as a “permanent” product A wave’s potential for growth is naturally limited. As a wave grows, it tends to slow down.

  47. Why Google Wave? Wave’s Limitations A wave should not be regarded as a “permanent” product A wave does not, moreover, have much intrinsic structure

  48. Why Google Wave? Wave’s Limitations A wave should not be regarded as a “permanent” product A wave does not, moreover, have much intrinsic structure If a wave gets too big, finding the new content gets harder. In a busy wave, new blips may need to be re-posted

  49. Why Google Wave? Wave’s Limitations • So how “permanent” is a wave? • The USF-Tampa Library’s • website-redesign experience: • 6 project team-members • used over a 6-week period • 100-150 edits/day at peak use

  50. Why Google Wave? Wave’s Limitations • So how “permanent” is a wave? • The USF-Tampa Library’s • website-redesign experience: • 6 project team-members • used over a 6-week period • 100-150 edits/day at peak use • 5 waves, roughly 1 per week

More Related