Now that I’ve had a chance to play with Google Wave a bit and to hear what other people have to say about it I’ve noticed that a lot of people are disappointed and it seems to me that they have missed the point.

Google Wave is a platform, a framework, an infrastructure. It has a front end, but that’s not really what is impressive about it (which is a good thing considering the complexity and bugginess right now). What is amazing is that Google has developed a real-time communication framework that can work in a federated environment. Why is this cool? Because it means that I can use it at work behind firewalls, at home for my family and personal projects, set it up at school with the right privacy to comply with child protection laws and also participate in it publicly on Google’s servers or anyone else’s I prefer. And it will still work in real time, across these servers transparently to me or securely within them. It won’t be “a Wave clone” that I have to beg everyone else to sign up for. It will just be Wave on a different server. All my contacts can be shared and my communications flow as freely between them, or I can create a walled garden. The choice is will be up to me.

People aren’t getting it right now because they’re expecting the beta to all be about polishing the User Experience. But it’s not about polishing: it’s about defining. This is similar to the introduction of Microsoft Surface: here is a great big flashy table with a powerful computer in it that responds to touch. At first exposure it sounds awesome, but what can you do with it? How will people be most comfortable interacting with it? What practical tasks can it facilitate? What fun can be had with it? The potential is there, but the only way to really know how it should best be used is to have a lot of people attempt to interact with it, without preconceptions, to figure out what the natural ways to interact with it actually are. There have been a lot of surprises as more and more people are able to play with it. A whole new set of gestures and user interface elements have been developed for Surface and refined as more and more people actually use them. I had the opportunity to participate in part of that process and it was fascinating.

I see Google Wave’s release as very similar to Microsoft Surface’s. There is a really powerful back-end underneath the UI that is capable of some amazing things, yet there haven’t been enough people exposed to it for the development team to really know the best way to provide efficient interaction with that engine. I think that is the purpose of the closed beta, to figure those things out. But people have these unrealistic expectations based on the misuse of the whole “beta” concept that what Google has is just a tiny step away from being ready for release to the world. That’s just not the case. That doesn’t mean there isn’t a ton of potential in Wave, and, to those of us out there than can appreciate the magnificence of the accomplishment of the platform that Google Wave is built on, it is very impressive indeed.

To all you fellow beta testers out there: give it some time and give Google some feedback and you will see Wave become much more intuitive to use (as well as less buggy and more performant). Developers will build alternative clients and more and more widgets for it. Waves will become just one more format for communication that we won’t even think about, we’ll just use in the way that’s most appropriate for the type of communication we need at the time. There will be “client views” for particular tasks based on who you are communicating with and their accessibility. If they’re offline you will use an email-like view to compose messages to them. If they’re online, you’ll use something more akin to IM or Twitter. All the stuff that is currently confusing and gets in your way (scrolling down huge waves just to find the new messages) will be fixed to no longer clutter your experience. And you will eventually be able to customize your client to make it even more efficient for how you want to receive your information, not just how you create and share it. These things will come as more people are exposed to Wave and see the potential and write their own solutions to the new problems that are becoming obvious now that there are enough other people to interact with on the service.

It’s new, and in closed beta. It’s not fair to write it off as “over-hyped”, especially when the hype has been coming from people who were interpreting screen shots or didn’t really understand that Wave is a new platform and not really a new UI to “fix the problem of email” or become the next social media magnet site. Google let us beta testers try it out to figure out how we’re reacting to the new communications capabilities Wave’s framework offers. Give Google the feedback they need to make it better for everyone.

Wave offers us a new way to communicate digitally that is adaptable to our immediate situation and needs. Wave is not out to replace Twitter, Facebook, IM or email: the point is to render them obsolete. That will happen without a lot of protest once someone figures out the ulitimate client for the already amazing platform Google has built… it will just seem natural.