It just announced that Google Wave, the bad boy of the house, opens its infrastructure, so that may be installed on other servers. Many have interpreted this as the true beta of the product, which will realize their potential.
In the twenty-fourth sharismo synchronized, Carme Pla he puts his hand to his proposal that I sent, what Google Wave solve problems?, An article by Daniel Tenner, cofounder of Woobius. Porfa, do not forget to visit the version published in the Carme blog.
I must confess that after a frenzied first days of exploratory Wave, at the invitation of Antonio, I almost made it stand by for the moment I see no short-term applicability in my digital life, which does not mean the will have soon. Moreover, certain that he will be, will come from the hand of fully-fledged geeks than me;)
In recent weeks I have read many blogs published analysis of reference and also browsed the occasional guide or training materials, eg of Mashable. Some thoughts I have seen remarkable Blogoff, Versus, Cuesta Jaime’s blog, Web Masters, Error 500, Wwwhat’s new and, of course, the shell.
But perhaps the best definition I found in the Wave Blog Andrés Nieto: the result of an orgy between a forum, MSN and a Wiki. It seems that at least fun is guaranteed;)
I leave you now with the translation of Carme, and you advance one of the most important paragraphs of the article:
Wave is not a social tool. There is Twitter, GTalk not, is not Facebook. Never was designed to attract the masses of geeks who are testing it now. Wave is built for the corporate environment. It is a tool to run work.
The image is of flap.
What Google Wave solve problems?
For most geeks, the main problem with email is spam. They have no problems with online collaboration – using Google Docs, Etherpad, Skitch, tools, screen sharing or collaborative whiteboard numerous applications. So the biggest problem is for geeks who have subscribed to all services that are swamped with reports, monthly newsletters, automated messages, and a small amount of spam that gets through the GMail spam filters. But when they want to collaborate on a document or image, know how to find the tools they need, most of the time.
Nevertheless, most geeks do lots of collaboration based on documents, email or otherwise. The programming does not require large amount of collaboration tools beyond source control and bug tracking systems. If you’re Robert Scoble probably do not have to spend days working on a specification document for a delicate aspect of Project X, or at least not very often, and probably not the suggested changes which collates worldwide and returns to send the document to be reviewed again.
In most corporate and business environments, however, this happens all the time. People work on documents, presentations and more. They maintain long conversations via email. Jobs come and go through one or multiple organizations for weeks before being completed. People who join the conversation later. Attached files are lost. Inboxes are filled and emails that are stumbling. Great suffering.
What are the problems with email in the corporate environment, and what makes Wave to solve them?
Problem 1: Work in a text
It is difficult to use email just as it is used, for example, Etherpad – to collaborate on a document to be sent later. Most of these collaborations they end up with either a Word document with tracked changes, or when they are more timely, in a long chain of emails with corrections coming from all directions. It’s a nightmare to track and collate all the feedback. Even giving the answer is difficult at times: we must cite the context and make sure the change is clearly highlighted.
Google solves Wave effectively integrating the features of Etherpad and email client. It is a breath of fresh air.
Problem 2: Add new people to the conversation
A common thread can forward all email to a whole new entrant, or list it in the following answer, but what will that person is messy and confusing, in reverse chronological order. If you have ever added to a thread of email over a week and it contained dozens of responses, you know what I mean.
Google solves Wave giving exactly the same vision to everyone, regardless of when they were added.
Problem 3: Keep people added added
Many times when new people are added to a conversation, you lose again later when someone replies to a previous email which included no new entrants. Sometimes it costs a bit until you realize that there are people who are not in conversation. It takes time and is annoying for all those who are and those without.
Wave solves this problem by having “let out to people” is an explicit action and not something done by mistake ..
Problem 4: Attach files
Most large companies have an email storage problem and limiting the size of inboxes. For this reason, it is not uncommon to see notices of “mailbox full” when we send large documents. Not only that, but can be risky to send documents. The SMTP protocol does not seem very good to send large files.
Although in truth, Wave will probably suffer the same limitations as other applications HTTP file upload – but it remains far better than the current email. Send emails over 10MB usually fail. Append a 10MB file in Wave is no problem at all.
Problem 5: Attachments lost
When we respond to email an annex, the annex is lost. This is good for email, because it prevents a single thread unnecessarily clogged email server storage while its bandwidth. Since all email is transmitted by the cable when you click “send”, such limitations are inevitable.
What this implies, however, is that if you get new people into the conversation, adding them as recipients or by returning the last email in the conversation, have no annex. Not only that, but if we find the first schedule, and the conversation takes weeks (and most people usually receives around 50 emails a day major), found that Annex can be quite difficult. If there were multiple attachments for the thread of conversation, group them all and send them to a new entrant is exponentially more tedious.
With the Wave model, however, the annexes are kept at the site were added. Only transmitted by the sender wire to the server once. Never forward an attachment to someone. When you add people to the conversation, gain access to the annexes at the same time.
Problem 6: Multiple branches of the conversation
Email conversations are basically flat. If you try to create multiple branches in a email conversation ends with a sordid confusion. It may have done a few times in life, but you learn quickly not to do so. But flatten everything has its own problems of sharing – each email ends containing answers to several other emails. It becomes very difficult to keep track of what has been answered and what not. And it is difficult to consolidate all the suggestions effectively.
Google solves Wave wireless enabling crystal clear. Yes, if you use lots of threads of conversation on the type of instant messaging will be difficult to manage. But with email threads collaborative kind, help keep things more orderly.
Problem 7: Small corrections
With email, the only comment if another email is the correction of a dozen typos, it should be almost as much work as if it were to make substantial changes to the proposed text. We have to cite the context to highlight how much is correct, then trust the other person to apply the changes to the original document (which often forgets to do – after all, are only a few misprints).
With wave, there is no such problem – you can simply edit the original text and make those changes. If the person who wrote this document seeks to review the changes made, you can rebuild.
Problem 8: From Email IM to Email
Instant messaging is a useful and powerful technology that has proven its worth. But it is well integrated with email. For those who trust in the inbox to continue the talks, there is still that gap in order to keep IM elsewhere. GTalk attempted to resolve this problem by storing the IM conversations in the inbox – and it was a good step.
What makes Google Wave, however, is much more prominent: it recognizes the fact that many IM conversations, in corporate environments, starting with an exchange of email that is just too fast. When sending more than 3 emails to the same person in a minute, often make more sense either call or go by IM. With Google Wave this need not be a conscious decision: if you answer quickly, Wave becomes an IM platform without any transition. When responses are slowed again then converted back to email platform.
This means that the entire conversation, whether as type IM-type email, is susceptible to monitoring or do a search on the site, visible to all who have been invited to the conversation.
I think people who do not see why Google Wave is simply viewed from a perspective inadequate. Wave is not a social tool. There is Twitter, GTalk not, is not Facebook. Never was designed to attract the masses of geeks who are testing it now.
Wave is built for the corporate environment. It is a tool to run work. And here is an excellent tool, even in this early state in which it is.
It will probably take years before it completely penetrates Wave large corporations and replace the email system to which everyone is accustomed. But solving many complicated problems with email that can handle very well, unlike many other attempts to fix the email you have failed.