Google IO Update

In MasteringWave, we have been developing a wave application for a long time. We are about to think that the application is ready for external feedback. It is in no way complete, but we would really like to show what we are capable of making this happen and get some feedback on how the application is working.

We could probably continue to develop on the application for the next three years and then make it available to the public to get response. But it is really important to get response from the market.

We are therefore happy that we have a boot to show of our project at Google IO next week. It will be exciting to see how people find the application and are sure they find it useful. If you want to get early access to the application, be sure to sign up to our newsletter. Then we will provide you with an early access link.

If you will be at Google IO be sure to drop by at our booth in the Developer Sandbox area and have a talk about how Wave can be used in your organization.

Here is the link to our Developer Sandbox,

Removing Participants in Google Wave

Google Wave is living up to its promise and now you’ll be learning about how to remove participants from a wave.

If you are the one who have started the wave, you have full control over the participants you wish to remove. And, the only participant you cannot remove is yourself since you are the one who created the wave.

To be able to remove a participant from a specific wave, all you need to do is click his or her picture, which is located at the top of the wave, and then click “Remove.” If you have done this successfully, the participant will only be left with a read-only copy of the wave and he or she will no longer have access to whatever content you will be adding on the wave.

Also, if you have removed a participant before they have actually opened the wave, the entire wave will disappear from their account.

It’s good to know that Google Wave continuously develops helpful and easy-to-use features so watch out for more and keep posted!

Book review: Google Wave Preview Explained

I finally purchased my first book on Google Wave. It is Google Wave Preview Explained by Ted Husted. The book completion date is the 24 of November, so I doubt that it has went thru a long review process like longer books contains. I don’t see any problems in the content, though the fast production. Some of the book is online at while the book can be purchased on Amazon for 16$. The book has 120 pages and is read fairly fast. 41EtZ-U4OlL._SL160_

The audience is people not familiar with Google Wave, how want to get up to speed. If you spent some time on getting familiar with the content of the book before you started to work on wave you would save a lot of frustrations. The concepts in the book are explained really well, and mean you don’t need to use trial and error.

One of the interesting topics is how Ted Husted in one line explains Wave:

Wave combines elements of email, instant messaging, and content management into a unified, easy-to-use environment.

I have always used Wikis instead of content management systems. When I think of a content management system, it is some place where few people are working like creating an external facing portal using Joomila or Microsoft CMS. There might be more to CMS than you first would think. I’m not sure either way is the best way to describe the concept of Wave.

The book starts with a nice example on when Wave will be useful in business context, compared to email. This is a great way to show why Wave is superior and show of some of the everyday issues we have with Email.

Ted mentions use of Wave as a way to distribute porn. At the moment I will not be so afraid of this because Wave, because Wave is currently not medium for mass distribution. Porn will be shared with probably with the help of spam bots, we just have to wait for this to occur.

Ted also mentions that public tags only should be created by the owner of the wave. I would not agree that it is true. The more tags the better and more distinctions you can get in the wave and taxonomy.

The book as a good section on alternatives to using Wave, I found it interesting to read about what Windows Live and OfficeLive could help with. These two tools could be a competitor to Wave, and it could be useful to know how they work. There is also a mention on etherpad, what was purchased by Google last week.

I was irritated by all the ads in the book. I have purchased the book, so why should I get ads instead of content. It is not a magazine, where I have agreed with there should be ads.

It is a book that will be revised because there are a lot of areas in the book there need to be clarified when Wave is developed future. There is a lot of placed To be determinate, and this depend on how Wave will be implemented.

For new users of Wave it is worth investing the 16$ in purchasing the book and save many hours of disappointment. It is a book with a limited life time because the next revision should be created soon.

What to do before the Google Wave invitation arrives

I’m currently waiting for invites to the live Wave system,. The sandbox works still fine, so I can still collaborate. So an obvious choose is to follow up on what is happening and research for news. Try to have a look at the API’s for the system, and then you can start your development. Try to get the AppEngine plugin up and running.

There are some interesting blogs, to read for the day. ReadWriteWeb has an article on what to expect from the Wave launch, this gives some interesting pointers to how the launch will take place. Among that you can nominate 8 friends with invitations. There will be no new features for the wave system.

Lars Rasmussen and Stephanie Hannon wrote about what he google blog. They write about the teams process and the fun they had when they was at a school and had the children write stories together. Lars and Stephanie believe that people will be more productive with wave when communicating and collaborating, which I believe is a large part of the day. I would have to agree with them.

Stephanie Hannon also wrote about what happened in the wave sandbox on the google blog. She mentions the SAP and Sales force as some of the vendors how have made some impressive demos of the potentials.

Stop checking the twitter channel for #googlewave, it is way to full today so you will just get a lot of messages. It is really difficult to follow the conversations. The just wait till people starts receiving the team had received of feedback and the use cases which was presented from the sandbox period.

So when you get online try to check out the maps gadget, Pamela Fox has made.

Then hope that you get an invitation. I just hope that I get an invitation for my domain, so I can start collaborating with the team.