Well, now it’s July and I don’t see any of the above really having been fixed and I’ll add to the list:
I want to print or export a wave to another format. I’m working collaboratively on creating a document I intend to print and the best option going is a bot named “Ferry” that pumps my Wave items into Google Docs where 2 steps down the line I can export to PDF or print.

I use wave daily for our internal communications between the members of my wedding band. Unfortunately, since there’s no mobile client, the drummer of the band can’t join in. This is a real killer one for me. If there was just a mobile client, I know scores of people who’d join the revolution!

Great post… I agree with your list of 10 improvements needed to Wave, particularly with the need for some form of author ownership/ super user type functionality within Wave. I think this is actually partly why Facebook applications/ events are particularly useful because they allow authors to delegate privileges to other participants, whilst maintaining overall control…

Think as you rightly mention in points 2 and 3, the business world is very different and if/ when Google Wave is fully embraced within this medium some form of permission workflow is indispensable… For example, think of taxation accountants that handle payroll information on a daily basis.. Although I’m not an accountant by any means, I know their permissions operate on salary brackets for who has access to whose salary information…

But, on the other hand, Google Wave is all about open collaboration so maybe the presence of ownership and control is against this mentality…? But, as your points rightly say and something I agree with, the use of Google Wave in business needs to embrace this difference.. Maybe the options for wave accessibility, namely private and public need to be addressed, maybe further categories are needed, maybe even with pre-set permissions etc…

Anyway, thanks for the post, looking forward to the next one David,
James

In response to: Enrico Poli January 4, 2010 at 11:16 pm
Hi everybody,

I’m surprised to see this not listed it: maybe it’s already possible and I’m not aware of it… anyway: I’d love to be able to save or back-up a Wave. I’m putting on Wave important thoughts and documents, and the only way I have to save them is copy and past each single blip. Restoring a deleted wave would be a time consuming mess.

So I’d like a simple way of exporting a wave (ideally, in some xml format) and importing it back if it becomes corrupted or if it’s vandalized. That can’t be so difficult, can it?

If you have Adobe Acrobat Extended and a Website, you can post the wave to a URL With iframe http://wave-ide.appspot.com/iframe.xml
and then create a PDF from a website. I know this is a lot to do but it has worked for me.
Karl
.-= Karl Sydow´s last blog ..Industry Mashup’s – Remix Innovation =-.

I couldn’t agree more with the need of a delete Wave by author feature and the ability to remove contacts from the Wave if I create it. in addition to your list there are several items I would like to see:
1. The ability to delete Ping blips.
2. Removal of blips, from the Playback.
3. Removal of Blips from removed extensions/bots.
4. I would like the actual invitations sent to me instead of directly to the invited person. (I have sent out several invitations and the people have no ability to get them up and running. If it were sent to me I would put togeather a package of all the necessary steps and links to guide them through and attach the actual invite.)
5. if I send an invite to the wrong email, I would like it back. I am running out of invites because half the people give me the wrong address to send it or they cant get it installed.

Karl
karlsydow.com

The idea of being able to totally delete a Wave seems to be one most folks (that commented anyway) took some exception too.

My idea behind that was from a business prospective…let’s say I want to collaborate on an idea with a few folks. Once finished I didn’t want any record of that Wave anymore for whatever reason.

It is like having a piece of paper or working on chalk board on white board and erasing it. It shouldn’t be for everything. But it is a value function from a business perspective. Same as owning a Wave and controlling who can enter.

Both of these improvements would be valuable to business workflow. Heck we have closed door meetings every other day at my work, where we white board out some ideas but make damn sure we erase that sketch for not all to see afterwards. In big business they take this stuff very seriously. They would not want ideas living forever in the cloud.

Keep the comments coming! Great discussion and I love to hear the counter opinions.

… I should add improvement 11) for me would be that wave would be more stable and speedy. I’m expect federation to play a big role in that.

I agree with most of the suggestions, but suggestions 2, 3 and 9 are really off the mark in my modest opinion.

If someone forwards me a wave, I don’t want someone else to be able to delete it. Especially not if I participated in the wave.

Owner only invite, hell I suppose it could be an optional feature, but really why add to the bureaucracy? With e-mails or documents people can add contributors without having to go back to the owner, it’s something called trust in your employees I believe
.-= JamesR404´s last blog ..JamesR404: @huskyr Nog een reden waarom het digitalizeren van boeken zo belangrijk is. http://trunc.it/4l0is =-.

Pretty good post. what I would add though is some form of notifications since you curreny can’t determine if people reply back to your comments on the wave unless you use chrome with the wave extension, are logged into your google account, and refreshing your page constantly. Kind of annoying.

Also to comment on 1. Google is working towards doc collaboration. They recently acquired Etherpad (a easy to use doc collab service) and have assigned there team to be a part of Google Wave. If that isn’t a sign I don’t know what is. 2010 will usher in a new wave

Chris Nwakalo