Applications My Opinion social media

Social Media Killed Google Wave

On Wednesday Google announced they are pulling the plug on Google Wave. Yes, this will piss you off, but this needs to be said:

Social media killed Google Wave. Or at least social media was instrumental in its demise.

Why? Because the people who fell over each other and sold their grandmothers to get an invite to this much hyped communication invention were not the people it was intended for and they did not need it, want it or know how to use it. As a result it was left, like an unsolved Rubik’s Cube, by the wayside to die a slow death – not because it was faulty or lacked uses but because those of us who had it didn’t understand it, grew tired of it and simply forgot about it all together.

So how did this happen? Winding the clock back to last year and you’ll be sure to remember the insane frenzy that was the battle to get a Google Wave invite. Everyone and their grandmother (before she was sold) wanted in on this revolutionary “real-time communication platform” from Google. The video demos were awesome. Silicone Valley was all abuzz. The gadget blogs, geek blogs, dev blogs, social media blogs, tech blogs, mom blogs and cute-dog blogs were talking about it. The Twitter Fail-Whale got face time over it. Facebook became a trading ground for invites. It was truly crazy.

The description tells the story

But why? All the videos, the writeups and the demos showed the same thing: Google Wave was a real-time collaboration platform that allowed groups of people to work on the same project at the same time – in real time. Which is something that’s done. In organizations. And in companies. And that’s about it. Normal people, like me and the vaste majority of the social media herd, do not need nor use such collaboration platforms because we don’t work on projects where they are needed. And before you say “oh, but Google Wave was something new and different that I needed in my life” remember that there are already several services out there that do part of what Google Wave did that you rarely, if ever, use.

I remember sitting at my desk in those days and thinking “what the hell are people going to do on Google Wave anyway?” I kept seeing Facebook and Twitter updates like “I’m on Google Wave right now! Anyone want to chat?” and I thought “Why? You’re already on a different platform chatting about chatting somewhere else.”

Don’t get me wrong here. I was part of the frenzy and I got my invite and peddled invites to all that asked. I was just as bitten by the bug as everyone else. And I’m to blame for Wave’s demise as everyone else.

Don’t knock it ’till you’ve tried it – for real

When I finally got my invite it was for a reason. We were in the process of planning the first 12×12 Vancouver Photo Marathon and needed a way for the 6 members of our team to work together on a pile of disjointed odds and ends. My partner in crime Angela decided that Wave might be a good platform for this collaboration so she set up a wave for us to play around with. After watching some videos and reading some of the documentation she quickly became proficient and set up a really impressive wave with images, documents, videos, chat and map integration. The problem was noone else in the group had time to get familiarized with the app so Angela ended up working on it pretty much on her own while the rest of us just watched in awe.

What I saw was huge potential – if there was a huge project with a multi-tiered team in several locations involved. What I realized was that this thing was not made for me, my company, my coleagues or anyone I knew really. It was made for large corporations or groups with highly complex projects that require real-time data and content management.

And that was, and is, the crux of the problem: The people on Google Wave were not the people who would benefit, or even find useful the functionality of Google Wave. Thus it was discarded as a neat looking but useless Beta.

Too much, too soon and to the wrong people

In the wake of Wave’s demise a lot of people are saying it buckled because it didn’t have enough to offer, that it was too complicated and that it didn’t have an actual use. I disagree. Google Wave was something truly remarkable that introduced a whole new way of collaborating and creating content. The problem was the people who would actually use it were already using other more established platforms or were drowned out by the masses that were so eager to jump onto the newest and shiniest bandwaggon that they didn’t realize the band was playing atonal black metal jazz with clarinets. Sure, it has it’s followers, but those were not the ones hitching a ride.

Additionally I think Google Wave was a bit too forward thinking. In a nutshell Wave introduced a type of non-linear stream-of-counsciousness workflow that is hard for people to wrap their heads around unless they are already used to it. Although real-time collaboration might sound cool it takes time to get used to writing a document while watching someone else edit it. And it takes even more time getting used to having multiple conversations in multiple streams at the same time. Sure, social media is pushing us in that direction but we still have a long way to go. We are still too stuck in the linear task-oriented way of doing things to be able to incorporate this type of workspace into our lives and offices. It’s coming but it’s still a few years away. Google simply pushed the envelope a bit too far and it fell off the table.

What can we learn

Like I said, the problem with Google Wave was never the app itself but the people who (didn’t) use it. This begs the question “Why were these non-users involved in it to begin with?” The answer is social media hype, pure and simple. Everyone was talking about it. It was touted as the hottest thing since an overheating MacBook Pro. Everyone just had to have an invite. People actually paid money for invites. But noone (myself included) ever took a step back and asked themselves “Am I actually going to use this thing? Is it even for me?” It’s pretty clear that Google had asked, and answered these questions and that both answers were “No!” Which is why the Beta was closed. Unfortunately the closing of the Beta seemed to have the unintended effect that people thought it was cool to get an invite, that they were part of something new and revolutionary, so rather than the Beta staying closed within the groups that were actually going to use the device it started spreading out to nerds like myself who just wanted their share of the fun.

Regardless of how it actually happened the result was an almost vertically accellerating growth in users followed almost immediately by a vertical drop in actual use. Not because the app was crap but because the people enrolled in the Beta testing were not actually Beta testing or doing anything else with it.

The conclusion? Hype is just hype. It is not a measure by which you should make decisions on whether or not to participate or buy something. And closed Betas are usually closed for a reason: To get actual results from actual users. And maybe most surprisingly: Social Media has the power to destroy great things simply by overloading them with massive interest followed by complete abandonment.

Rest in peace Google Wave. We hope to see you again in another time.

Applications CSS Tutorials

Create a Twitter Box in Your Sidebar – Part II

My Sidebar Twitter box tutorial seems to have struck a chord with WordPress users and it has generated some interesting questions. One of them, from TheNext2ShineBlog posed an interesting problem I decided to look into in more detail:

the only thing I would like to change is the time aspect (23 days ago // 4 hours ago). Is there a css code to hide that link without taking away the links from the original twitter message?

What TheN2S is refering to is the tail end of each Twitter message that reads either “less than a minute ago”, “a few minutes ago” etc up to “X days ago”.

Careful inspection of the JavaScript that generates the Tweets for the application (found here) shows that the time information is a core function of the Twitter system so it is coded into the main structure of the application itself. Therefore it is hard to siply remove it unless you want to create your own custom JS. But TheN2S is on the right track in asking if it can be removed by way of CSS.

Lifting a random tweet off my own site I found that the main body the JS spits out is contained within a span tag while the tail end with the time info is not:

  • @webb_art DropBox works well for me and is platform independent: about 15 hours ago
  • That means we can use CSS to hide the content not in the while maintaining the visibility of the content that is. That requires some additions to the original CSS code:

    #twitter_div ul li span {
    	visibility: visible;
    #twitter_div ul li span a {
    	color: #D78E42;
    	visibility: visible;
    #twitter_div ul li a {
    	visibility: hidden;

    The first two single out the regular and link contents within the span specifically and set their visibility to visible. This is done because the last style sets the visibility of all anchors within list items under the twitter_div ID to hidden. So we are really working backwards – first hiding everything and then unhiding it in particular cases.

    By adding these three style elements the time information will be hidden by the CSS while everything else shows up normally.

    Move the time and date stamp to its own line

    A couple of people have been asking how to separate out the date and time stamp and place it on its own line. The answer is to target the same span above and set its display property to block. That way it will be separated out. I never got around to answering it but reader thnhzng posted a nice piece of CSS in the comments that I thought would be worth pasting in here:

    #twitter_div ul li span {
    	visibility: visible;
    #twitter_div ul li span a {
    	color: #D78E42;
    	visibility: visible;
    	display: inherit;
    #twitter_div ul li a {
    	display: block; /* creates line-break b/f & after */
    	text-align: right; /*aligns time-stamp to the right */
    	font-family: 'Trebuchet MS'; /* change t-s font */
    	color: #445566; /* change color of time-stamp */
    Applications Vista

    A better desktop with RocketDock and Vista Start Menu

    Sitting in front of a computer about 80% of your working day it is important that your work environment – that is your desktop – is both visually pleasing and functional. Having switched to Windows Vista not too long ago and just bought a new laptop I spent some time customizing my desktops to increase functionality and decrease clutter. Along the way I found some useful applications and some nice tricks that I’d like to share with you.

    Get a Dual-Monitor Wallpaper with DisplayFusion

    One of the things that has bugged me from day one was that out of the box neither XP nor Vista allowed you to have different wallpapers on different screens if you have a dual screen setup. I’ve been working with two screens for years and a cohesive background graphic for my workspace has always been one of the items on my wishlist. When I came across the beautiful Mandolux multi-monitor wallpapers I decided that now was the time so I started digging around on the web for a small app that would let me split my desktop in half so to speak. After some trial and error I landed on DisplayFusion – a free multi-monitor desktop wallpaper application that runs on both XP and Vista alike. The application is light and easy to use and combined with a Mandolux wallpaper the result (as seen at the top of this article) is quite stunning.

    Keep your tools handy with RocketDock

    It’s no secret that I’m a Windows guy and I have less than kind things to say about it’s rival the Mac. But that doesn’t mean I’m not willing to say that Steve Jobs and his fruity company hasn’t come up with some briliant ideas. Ideas like the customizeable launch bar. Fortunately clever coders have created several clones of this application that run in Windows environments. One of these is the nice and spiffy RocketDock. It lets you drag and drop any application, folder or whatever else comes to mind into a dockable launch box and makes them available to you with one click. I’ve installed it on both my office computer and my laptop (as seen below) and moved the regular Windows Taskbar to the left hand side to get it out of the way. Now I have all my frequently used applications handy with one click at the bottom of my screen and if I want to dig deeper I can always go to the Taskbar. As Candide would say, it’s the best of all possible worlds.

    Harness the launching power of the Vista Start Menu

    An often overlooked application that I myself wasn’t fully aware of until recently is the Vista Start Menu search box. More than just a regular search box, this powerful feature lets you launch any application by simply writing (part of) it’s name and hitting Enter. This comes in handy when you want to launch a seldom used or hidden application like the equally genius Snipping Tool which for some bizarre reason is hidden within Vista. The search box catalogues all your applications and lets you launch them without digging through folder trees on the Program menu.

    “But wait. That’s exactly what Launchy does” you might say (if you’re a real nerd or a Lifehacker reader). And you are right. But think about this for a second: Why would you use a third party application to do something that has been built into the operating system anyway? Sadly the prevalence of Launchy and applications like it on Vista systems shows how buggy the transition from XP to Vista has been. But fret not: If you’re already a Launchy user, try switching over to the Vista Start Menu for a while and you’ll see that you can safely get rid of that extra 3rd party bulk and still get pretty much the same results.