Ever since Google launched email services through Gmail, the most exiting communication service Google offered was that of Google Wave. In plain terms, Google Wave could be described as a mixture of Twitter, Google Docs, instant messaging, Flickr, and had the provion of being blended with robots by developers.
Wave was different from email, in that rather than being a two party form of communication like email is mostly used for, Wave was a forum of two or more people. A wavelet, on the other hand is a small community – maybe a party sharing their feelings in a discussion, and later with the option of joining a bigger wave. On the other hand a Blip, Google suggests, was the smallest group.
Though Google Wave is similar to email in sharing messages and interacting with each other, it had more functions. Importantly Google Wave Robots were the non-human participants in the interactions on the Wave, performing assigned tasks such as posting on Twitter, deciding price comparability, and were limited to routine duties. They hadn't proven to be very popular.
Google Wave was launched in 2009, but developers had at first experienced some difficulties, like crashing, the infrastructures inability to handle message traffic, traffic from people out to have a preview etc.. Like one of Google's other servives Blogger, it was a type of hosted media, and was categorized as a Google Apps feature.
It was also a platform in the sense that it allowed developing institutions to create various apps and works in coordination with the likes of Google Maps, to bring out apps on a third party basis. Google Wave was considered a Protocol, helping others using ‘wave federation protocol' or institutions to run servers on their own. Though it is like email, using the similar process of exchange of messages, wave users should use the same system of addressing by usersname@domain.
The product was intended to be the next generation of communication and an open architecture was provided to allow other providers to host their own Wave services.