Why is Google Wave so intriguing? Because of:
- Its core capabilities. Google Wave enables enhanced communication between multiple users in communication packages called waves. Waves are like threaded emails on steroids. It is possible for a user to insert comments in the middle of a wave, link waves to each other, add a participant to the wave at any time, use the system like an instant messaging (IM) system to deliver real-time comments or like an email system to deliver fully formed thoughts, collaborate on a document and show or hide revisions, rewind the wave to see its detailed evolution, and to apply privacy standards to portions of the conversation. And those are just some of the highlights.
- Its open protocol. One of the reasons Google received a large amount of media attention - traditional, community site, blogger - is because the for-profit company is making the protocol open and available to all. For example, those interested can read about and begin to build competing systems based off of the draft Google Wave Federation Protocol (see the official site here). This protocol is critical as wave systems are designed to be federated - a fancy term for allowing seamless interoperability between systems administered by different entities, including public service providers like Google and private organizations.
- Its extensible design. While the core capabilities Google showcased at the conference highlighted some powerful new ways to communicate and collaborate, the extensible architecture of the wave system will enable developers to significantly enhance Google or other wave offerings (read about the APIs here). In the same way public map APIs for services like Google Maps enabled amazing new services and sites, the wave APIs will enable embedded capabilities, connectivity options, and other enhancements that will make Google Wave and its competition even more compelling.
With its core capabilities, its open protocol, and its extensible architecture, Google and many others imagine how wave systems might not only replace traditional email, but also replace proprietary IM systems like AOL's AIM, social networking messaging and site posting services like Facebook's Wall comments, short messaging offerings like Twitter, WebEx-like conferencing solutions, and other communication and collaboration services.
Big dreams, big hurdles
While Google Wave is appealing to many in the industry in terms of its goals and current execution, even at this early pre-beta stage of its life, there are some massive hurdles to overcome in order for wave systems - from Google or any other company - to be successful. Top problems include:
The good news for wave advocates: Communication is reaching a breaking point with disjointed services
- Everyone needs to be on a wave-capable system. To enable any of the rich communication described previously, all users need wave-capable systems, either from Google or from other providers. This is fundamentally why Google designed the system to be federated - that is, make it work with a series of distributed wave backend systems from Google, other vendors, ISPs, organizationes, etc. - and to make its protocol open. If only one side of a one-to-one or one-to-many conversation is wave-capable, the rich functionaiity is useless. Which leads us to point No. 2 ...
- People must accept and embrace the wave client experience. While Google made clear that wave frontends may differ depending on who develops a wave system, the most important point from an end user perspective is that a user must be willing - or be forced, if a requirement of a job or a project - to learn how to use a wave interface with its much more complicated layered, embedded, and ever-changing views. While Google engineers and technophiles may salivate over the usage and interface possibilites, user may not know, understand, be trained, or care about these features. To them, a complicated, multi-person wave may be an incomprehensible mess. Add to this the ability to extend the wave system and significantly change how it behaves or looks, and the issue of ease-of-use may turn off many potential users.

The good news for wave advocates: Communication is reaching a breaking point with disjointed services
While a wave system and its client front end might repel some users due to it complexity, the fact is that people today - in their personal and work lives - are jumping through amazing hoops to communicate with a massive range of disparate systems, each with its own interface and quirks. For example, a typical minimal set of communication tools for a well-connected person these days might include seven or more accounts (it could be more or less, depending on IM choices, social network memberships, etc.; see below)!
A non-technophile - soccer mom, granddad, or waitress - might need to check:
- Email. The simplest form of electronic communication, it can be one-to-one or one-to-many. It is asynchronous, meaning the two participants don't have to be communicating at the same time, though it can end up being very much like chat if the participants respond quickly. Attachments of any size and type - photos, music files, documents, etc. - are relatively easy to send and receive.
Required: All that is needed is an email account, either from an ISP (e.g., Comcast, Verizon, etc.), a personal domain (e.g., newrowley.com), work, or a Web-mail provider (e.g., Yahoo Mail, Microsoft's Hotmail, Google's Gmail, etc.). Interoperable standards (e.g., SMTP, POP3, MIME) mean that no matter the service type, the email should get through, though their will be different capabilities around features such as formatting, attachment display, etc. Despite interoperability, people tend to have more than one email account (e.g., one for work, at least one for personal user), and most don't aggregate the accounts - or can't - into a single reader. - Instant messaging (IM). IM is really just short email-type messaging that is quickly responded to. Unlike Tweets, there is often no substantial limit to message length, but the nature of the communication and the disjointedness of attachments makes it good for quick, back-and-forth communication with the occasional attachment.
Required: Users need IM accounts, usually separate from email but not necessarily so (e.g., Gmail users can use their account to access Google's IM). Differing IM standards mean that (Jabber aside), unlike email, users often have multiple accounts or rely on one network and thus limit their IM interactions. - Mobile texting. Like IM, cell phone texting is generally for short messages and the occasional image (through MMS). The line is blurred when users leverage smart phones with multiple communication capabilities (e.g., Blackberries or iPhones). A user may feel that she is texting (SMS), but the message may be handled by a different application with different protocols and capabilities.
Required: Mobile phone and a texting service (or a plan for reduced cost for frequent users) are required. Despite the tiny bandwidth required for text messages, the most aggravating issue with texting is cost. It has been pointed out recently that wireless companies charge an exorbitant rate for the service, apparently because they can, not because the cost is aligned with their infrastructure requirements. - IP-based voice and video. Audio and video calls, for example, using Skype, can replace traditional voice telephone communications - land and mobile - as well as traditional IM services (IM capabilities are a standard features of these types of services).
Required: An account with a service is required, but a user also must have access to the Internet and a computing device to run the client software (including a microphone and speaker/ headphones). While many traditional IM systems now offer voice calls, and many offer video, the systems are not interoperable, so membership in a popular service is critical. The result is a user might use AIM for IM needs and Skype for audio/video calls even though only one would be technically required. - Social network intra-site communication. All popular sites like Facebook have an internal system for communication (e.g., posting to the Wall for public messages, using the email-like messaging system for more targeted communication).
Required: A social networking account and "friends" who have approved each other to send and receive messages is the foundation of this type of communication. While some social networks and technology providers are moving towards some interoperability - at least they are talking about it and proposing some interoperable solutions - the reality is that most users have to maintain accounts in any site they find valuable. As a result, a typical user might have a Facebook and LinkedIn account, if not more. - Blogs, community site, and media property forums/commenting systems. For those who like to post their thoughts or engage in online debate, accounts are required at sites like The Economist, Slashdot, and Engadget (some sites allow anonymous posting, but then a user has no persistent identity and commenting history). For some people, this form of communication can be active and pushed if they sign up for RSS feeds and other notifications.
Required: Accounts with any sites that a person might want to provide feedback or comment at. This could be anywhere from one to tens of sites. - Twitter and similar services. The current poster child/media darling of modern communications is Twitter. The 140-character per message service enables users to post what they are doing or thinking as well as follow the comments of others, be it friends, family members, colleagues, or celebrities.
Required: Accounts with Twitter or other similar services are required. In addition to the accounts, the user may also invest in an application specifically designed to post their Tweets and display the content of all of the people they are following.
Wave service providers' to do lists
The key for Google and all wave system proponents is to ensure that the offerings:
- Work with existing communication systems, especially traditional email. There can't be an issue for users of choosing the old world or the wave world. Wave systems will need to be a superset of current communication systems, with backend services capable of tying into existing email, IM, audio/video and other technologies and protocols. The transition must be seamless - unknown to the masses.
- Hide complexity by default, only exposing advanced capabilities to those who want it. Technology companies are getting somewhat better at hiding complexity, whether it is with menus that only show what users need (e.g., the ribbon in Microsoft Office) or sliders and checkboxes for displaying advanced features (e.g., the iPhone settings). Video walkthroughs of products and interactive demos will help users learn about new wave-enabled features at their own pace.
- Let sites deliver branded experiences. Many sites, particularly social networking sites, don't necessarily want to be open. The concept of a walled garden always appeals to those with large, popular communities and to those that fear that being open makes it too easy for users to leave (and revenue to dry up). The idea of federated social sites, backed by wave systems, will scare most social networking executives even as they make life easier for users. Providers like Google need to ensure that waves can fit within branded site and service experiences in the short-term.
The reality, in the long term, is that many popular sites will die out in a wave-dominated world. The good news? As always, others will take their place (think of the histories of America Online, Yahoo!, and Google).
So, while wave systems are interesting, don't expect them ever to visibly take over the communication world. As they succeed, they will do so behind the scenes, slowly replacing the technologies and services that we take for granted today.
By: Tom Rhinelander