Whilst watching the fantastic Google Wave Video, here is a few thoughts I jotted down about things that Google Wave is going to need soon enough-ish to make it really really rock (not that it doesn’t really rock right now!).
- multiple google instances – at the moment you can’t log into multiple gmail accounts in the one browser – Wave seems like it will work really well if you have ALL your accounts in one place.
- multiple emails for one person – similar to above – how to deal with your multiple identities, especially since Wave will be used more in the workplace now too… I like the new service called MyHandle.com which allows all your emails to come to the same email address firstname.lastname@example.org and you then divert them to the correct email account.
- authority – is this person who they say they are – a continual issue for all social networks, and since this will be a business app too, it is very important
- spam – hopefully this will utilise the great gmail spam filters so hopefully it won’t be a problme
- anonymity – will you be able to blip anonymously?
- draft mode – they mentioned this quickly – the ability to control when the blip is visible.
- stop forwarding of waves – like the digital rights management built into outlook – control who can forward waves
- groups – I’m sure it would, similar to gmail groups – a quick way to send Waves to everyone in the company.
- google contacts needs to be sorted – Gmail contacts is really not ready for prime time yet – especially importing contacts.
- will it replace email? – Will I forgoe my gmail and use Wave exclusively? this is yet to be seen.
- notifications of content updates and ignoring all future notifications – Confluence has this feature, sometimes you just don’t want to know anything else about that topic.
- event and calendaring – this was sadly lacking from the demo – I’m sure it will be included but.
- not allow playback or remove bits from playback – some things may not want to be played back.
- real time markup of video – how cool would that be?
- making waves public – probably quite possible as calendar items are public – but maybe restrictions on who in the Wave can make it public
- Spell check for other than US – but hopefully, since it is built in Aus, they have thought of this.
- People who can keep one topic to one Wave – now since most people can’t keep one email to one topic, this one is going to be hard. But this is where branching off a Wave will be useful.
Do you have any other must haves for Wave?