I have had the opportunity to try out wave for my domain for the last couple weeks. I have used it on masteringwave.com. It has been a really nice experience and looks like it will propel wave in to the business side.
I have been using wave to organize my team’s efforts since we got started using the preview version of Wave. But it did lack some features that are really nice in organizational perspectives.
It is still in preview and there will be more changes to the wave system. So it is likely to change in the future.
I really like the way the group function. All your mail groups can be used as groups in wave. It seems like the groups are using groups for apps, if such a thing exists. It is nice that you only have to provision the users on place.
It is possible to see when you are Waveing with people outside of the domain. This is really nice feature, and allows you to see if it is a private conversation you are having.
Also as with Wave you get your whole address book, so you can communicate with the people on your list.
It is of course to communicate outside of your own domain with other domains. I have not yet configured anything in my DNS to allow this type of wave communication. I guess that it has to be configured the same wave you configure your mail domain. But since there are no third party waves out there yet the configuration is probably quite minimal.
We got access to see how it was to develop apps for a hosted wave service. It is quite possible, but we still have some issues that we need to figure out how to manage before we start using it to the public. But basically wave works just the same way, it is just not sure that all participants are from the domain googlewave.com anymore. So if that is hard coded in any robot/gadgets it should be removed.
We used Google single sign on to make it possible to sign-up to log on to our service. For this to work properly, our app needs to be a part of the Apps Marketplace.
When you create a wave in the domain, the wave id will be prefixed with the wave id. The Wave id is then longer then the waves from googlewave.com. It is a question if those waves also will be prefixed to fit into the structure. So, when all waves need to be prefixed with the domains, then all the current waves will not work. I suspect there will be a solution for this.
For the usability part of the application, it is really nice to just have one place where all communication, both for guidelines and day to day communication.
On Google IO we will be releasing our caseish.com app. Stay tuned to learn more on how that will help you.
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!