GOOGLE WAVE: An analysis of its untimely downfall + Google Buzz
GOOGLE announced the closure of Google Wave on their blog on August 4 after much hype from loyal Google followers. There has been much buzz as to why Google Wave was a failed project, but the pivotal reasons appear to be three-fold. Excessive hype and expectations, too many features for a single web application, and at the same time, not enough unique features to differentiate Google Wave from existing services (Facebook, Twitter), all ultimately lead to its untimely downfall.
The hype involved a handful of people being invited to test Google Wave and lead to several bloggers discussing it amongst themselves. After almost a year of testing and a plethora of blog entries, a lot was obviously expected of Google’s latest brainchild. However, there were still only a handful of people that actually knew how to make use of Google Wave and in an era of short attention spans and click-happy web-users, the buzz had just about fizzled entirely upon its release.
The problem was that for the average Internet-user to get to grips with Google Wave required setting aside a good period of time to learn how to use it, and for many, watching a video tutorial was essential. Google’s software developers even admitted that the service “takes a little getting used to” and that even they were still learning how to use it themselves.
Once Google Wave invitees got the hang of Wave they needed more people to be using it besides themselves in order to get a proper wave going. This proved to be difficult enough in itself, but perhaps the problem was not a lack of users, but rather a lack of appeal.
What exactly is Google Wave?
“Wave’s primary feature was to let users collaborate in real time, using an in-box-like interface that resembled a mix of Google’s Gmail Web mail service, and its Docs and Spreadsheets product. Each strand of messages, which could include text, links, and photos, was called a wave. Google launched the product with an API for developers to build extra functionality in the form of extensions that users could turn on and off” – Cnet News
I would argue that Google Wave had two other inherent problems. The first being that it did not offer enough unique features – i.e. things that web-users couldn’t already perform using existing Google and other services, and secondly that it tried to achieve too much at once. There also seemed to be a lack of focus with regards to what the product would primarily be used for.
To rope people into any new web service takes time and requires baby steps if you want to get enough people on board in order for the services to be worthwhile and developed further. The web-user trend is to stick with what’s foremost familiar and secondly to make use of the tried and tested. Although Google Wave offered several easy ways to perform familiar tasks online in real-time, the popularity of services such as Facebook and Twitter far outweighed its demand as a new web service.
Google has brought many great apps to the table that are worthy of praise and the Internet would not be the same without them; sadly Google Wave was not one of them. Until a viable market demand is found, the focus should be on improving existing Google services before unleashing something new to the online public.
A bit on Google Buzz
Google had another chance with Google Buzz – a web app released just prior to Google Wave. For those who are unfamiliar with Google Buzz, the service is an extension of one’s Gmail account – appearing below one’s inbox. It can be rightfully argued that Google Buzz is essentially a Twitter clone as it allows friends to provide status updates, embed photos and links, and to follow or be followed by other Buzz users. It now has a few Facebooky features too – these being the options of liking or commenting on other users’ posts and embedding photos and video.
The idea was to discuss “the buzz”, but from many users’ experience the service seems to be primarily used as a promotional tool for embedding links and directing peoples’ attention to them. Facebook remains the popular choice for status updating and the sharing of photos and videos and Twitter is still the first choice for posting something of real value.
I do not imagine that Google Buzz will ever become as popular (or perhaps more importantly – more popular) than Twitter or Facebook – least not until it offers something different to what exists already. Buzz needs to be able to stand on it’s own, which isn’t currently happening with the ability to Buzz on Facebook or Buzz on Twitter.
Perhaps bloggers and Google Wave testers are largely to blame for the excessive hype and ultimate disappointment of Google Wave. Perhaps it was the product itself that asked too much of web users by way of time and practical use. Or perhaps Google Wave simply did not fill a need in the World Wide Web by offering something entirely unique and different.
Google can surely be forgiven for the failure of Google Wave and hopefully learn from their mistakes. With a history of so many other great services and the downfall of only a few, support for future developments should by no means be tainted by their recent faults. Keep the services coming Google; you ultimately never know what will work online until you try.
- RIP Google Wave
- The official Google blog
- Google pulls plug on Google Wave
- Lessons Google Can Learn From Wave’s Failure