Google Wave: One Year Later
It is been a year after the first version of Google Wave was shown to some Google enthusiastic web developers and the press. How things have changed since then with Google Wave as a viable consumer offering?.
Not much, actually.
Google Wave continues to be a offering only suited to power users, the tech press and web developers. To the point where Google accepted that so by purchasing Etherpad; A more user friendly version of the same concept Google Wave is gunning for.
What has changed?
While Wave biggest achievement in the past year was to gain the stability and performance needed for it to be offered as a freely available Google App, lots of things changed around it as Google has adjusted many of their web strategies, and even released what could be seen as a competing (even if not fully) offering now known as Google Buzz.
Then there is Google Chrome, now at version 5 that got it plugin story changed radically as Google has downplayed and retired both Google Gears and O3D in favor of HTML5 and WebGL.
Google also decided to do a big strategic partnership with Adobe on all fronts and they decided that Flash will be bundled with the chrome browser, android and chrome os. Finally, on the NaCl front, things have been going slower than they planned and there is not really anything done Google had shown that end users can care to check for themselves at this point.
Those changes (Etherpad, Buzz, Chrome) have put the push for Google Wave to the sidelines. I expect that Google will start pushing for it again once the first full version of Chrome OS gets released to the public later this year. Also because until now i don’t see that what Google expected to get from Etherpad had been integrated into Google Wave. But being optimistic about it, we should do see it in the coming months.
Should it be retried now?.
Yes if you plan to use it for Liveblogging, Group Researching, Group Studying, Project Meetings or even as a new take on Online Chatting and Instant Messaging. Just remember about the logging, the replaying and the impulsiveness of it since what you say appears as fast as your think it and write it in.
The reason being its fully real-time wild nature that lets you have several people interacting into a communication stream overlapping into each other. Something that works well for a conscious transmission of text and media that don’t needs to be 100% fully coherent or clear. Just something that can follow a certain timeline, theme or idea.
No if you want to use it as a social hangout, network, community,forum, document collaboration,
The reason being that it is too messy for it. And if you got more than 10 people in a stream everything in it will end up in a bunch of senseless noise or something that would need to be edited several times over for it to gain a sense of order. Also because Google actually does offers you two other choices for things like that in the form of Buzz and Docs. That should be a clue that it only fits well for some specific scenarios and that while you can force it into others, it don’t means you should or that it will workout well if you do.
But if you are still keen on force it to do your bidding, you can check out what Novell among others are doing with the code of Google Wave.
Conclusions
I do not want jump into any final ones yet. I think that Google Wave still got lots of evolving to do in order for it to fulfill its potential. The problem is that not all the tech it needs is there yet and that it still lacks a huge lot of user controls, better settings and even better performance, stability and browser compatibility (Since it continues to be a good experience ONLY in Webkit based browsers) to really be able to judge it properly once and for all.But i will be doing just once a full year of my first post on it passes.
While that time mark would indicate Google Wave will have almost a year and half in the spotlight since its dev introduction. Given how Google develops things internally from ideas to alpha in around 6 months. That would mean it will have at least 2 years of continuous development by then. More than enough time to get some strong conclusions and even some final perceptions for the future of it on Google hands.
But in the meantime check it out for yourself now that is open for everyone. The only requirement is of course a Google Account.
Linkage
.
.
*Edited(03/06/10)*
Labels
Categories
Posts Archive
- February 2017 ( 2 )
- January 2017 ( 3 )
- July 2014 ( 1 )
- February 2014 ( 3 )
- January 2014 ( 5 )
- December 2013 ( 2 )
- November 2013 ( 2 )
- October 2013 ( 4 )
- September 2013 ( 7 )
- June 2013 ( 9 )
- May 2013 ( 1 )
- December 2012 ( 2 )
- November 2012 ( 2 )
- August 2012 ( 1 )
- March 2012 ( 7 )
- February 2012 ( 5 )
- January 2012 ( 15 )
- December 2011 ( 17 )
- November 2011 ( 6 )
- October 2011 ( 20 )
- September 2011 ( 19 )
- August 2011 ( 12 )
- July 2011 ( 3 )
- May 2011 ( 10 )
- April 2011 ( 7 )
- March 2011 ( 18 )
- February 2011 ( 10 )
- January 2011 ( 10 )
- December 2010 ( 16 )
- November 2010 ( 15 )
- October 2010 ( 15 )
- September 2010 ( 15 )
- August 2010 ( 30 )
- July 2010 ( 29 )
- June 2010 ( 7 )
- May 2010 ( 15 )
- April 2010 ( 20 )
- March 2010 ( 7 )
- February 2010 ( 10 )
- January 2010 ( 10 )
- December 2009 ( 27 )
- November 2009 ( 46 )
- October 2009 ( 23 )
- September 2009 ( 3 )
- July 2009 ( 3 )
0 comments :
Post a Comment
Welcome To Appatic.com
Please comment away. You can expect on me always replying to you if you direct the comment to me. Your comments do serve as a way to support the blog too, as comments in a post do help traffic.
Also do so to point out if a link is dead, an app has changed or to suggest a related app. That way i can fix or edit the post accordingly a lot faster.
If you liked this blog post, Please subscribe the blog feed using the link below:
Subscribe To Appatic