I spent most of today volunteering for the GO ON Barnsley campaign. Basically wearing a rather fetching t-shirt and badge (see above photo) and bestowing the wonders of this new fangled ‘internet’ thing to anyone who would listen.

It was a lot of fun and I’ll be doing the same again twice this month. I even helped out designing the ‘Barnsley’ version of the GO ON logo:

The GO ON Campaign, getting people online

Google, bless ‘em, officially launched +1 this week and the press is already labelling it a Facebook killer. Will this new stab at a product launch be a success? Or will it fall to the wayside like the ill-fated Buzz, Wave, Answers and the much loved but easily replaceable Videos?

What will make +1 a success where other products have so recently failed? I don’t know and wouldn’t like to guess – the only thing I can do is look back at these recent Google flops and find out how such an innovative and HUGE company could get it so wrong.

What went wrong?

In my opinion, none of the aforementioned products were inherently bad, they were just mismanaged. Some may have been flawed from the start and grossly miscommunicated but they were never really given the chance to evolve before being thrown aside and their resources placed elsewhere.

Lets take a look at this rouges gallery and see where they went wrong and in some cases, what could have been:

What went wrong with Buzz?

Google Buzz was essentially a proof-of-concept that was thrown together by Google employees to see if they could bring Twitter-style messages to Gmail – guess what? They could! So they did. But it was rushed to market and because of this a shit-storm erupted around privacy (or lack of).

But the REAL problem with Buzz was – nobody wanted it. Everyone who cared about microblogging at the time was already knee-deep in Twitter and didn’t want to leave. Google had a simple solution, link your Twitter accounts TO Buzz – which is what I did – ultimately making it just another useless social feed.

How could Buzz be saved?: Now, if Buzz was sold as a social aggregation and augmentation tool from the start it maybe would have been a success. I could happily see Buzz hooking into Twitter/Facebook/LinkedIn and even apps like Google Reader and Delicious to pull everything together in a single place – useful? I think so? Will it happen? No.

What went wrong with Wave?

Ah Wave! My favourite of the Google flops, why? Because I still have no idea what it was meant to do. I was blessed with a Wave invite not long after launch and probably spent no more than 7 minutes checking out the UI before shrugging and getting back to work. I mean, what was this thing? It wasn’t obvious? Some sort of email collaborate email, work-flow, document and task  system right? Wrong, well sort of.

To help explain this confusion further here is one of many descriptions of Wave features (via Wikipedia):

Waves, described by Google as “equal parts conversation and document“, are hosted XML documents that allow seamless and low latency concurrent modifications

Wut?

How could Wave be saved?: Its too late, the Wave platform lives on as the open source ‘Apache Wave‘ but its still a useless product with a small uptake – however, what if Wave had evolved into a Basecamp-style project management tool with SharePoint like online document management and One Hub style workspaces and widgets all linked into your Gmail inbox and contact list?

Sounds pretty damn cool right! HELL YEH! WHERE DO I SIGN UP! But no this never happened.

What went wrong with Answers?

Answers was a decent enough idea – real ‘quality’ answers to specific questions at a small price (a few dollars per-query). Think of it as eBay for questions. It worked very well for the period it was open and gathered a lot of useful content. But, it was a playground for lazy plagiarists and needed to be continually policed for bad-Answers and copyright infringements.

How could Answers be saved?: It doesn’t need to be. The idea lives on though sites likeg Yahoo! Answers and Mahalo with sites such as the infamous Experts Exchange and the new-kid Stack Exchange serving a similar product but to a more niche market. The Answers methodology is alive and well, I just don’t think Google had the stomach for it.

What went wrong with Videos?

Google Videos was YouTubes biggest competitor until Google bought them out – but for many (me included) Google Videos was a very different beast. It was less about ‘user generated content’ like piano playing cats and skateboarding dogs – the stuff that makes YouTube legend – and more about quality full-length online video.

I remember Google Videos being a dumping ground for excellent documentaries, training videos and even full-length movies. Sure, YouTube may have also had these hidden away under all the junk, but that wasn’t the point – the You in YouTube was all about your own videos, made by You and it still is today – even with the vast commercial changes.

How could Videos be saved?: By going back to the original strategy of digitizing offline content and publishing a high-quality, curated database of essential historic and educational video content. Things we can’t find on YouTube or anywhere else, things no one would even think to upload. Old movies, historic speeches, world news events, stuff like that.

This of course won’t happen – Google Videos has already been neutered and no new content is set to be added. Google are focused on making YouTube their only video service.

More Flops Products on the way!

So what else do Google have on the way after +1? Well, we have Google Music, which is currently in BETA and the Groupon-killing Google Offers. Both potential world beaters, if managed correctly. Both major embarrassments if not.

So that’s it – a brief look at recent Google slip-ups. But please, not NOT misunderstand this post – I love Google, I really do. Gmail/Andriod/Chat/Maps/Search they are all great products but I’m always let down by their attempts to do something new. They just seem to be letting themselves down time and time again and the negative PR-fallout is getting out-of-hand.

Don’t be Evil Stupid

My final word is that I just really, really hope the recent management changes will finally get them back on track so they can compete with Apple for music and entertainment and Facebook for social (sorry Microsoft).

I woke up to this earlier on my desktop PC:

This Spotify ultimatum irked me a little, I don’t mind being blasted with ads after ever couple of tracks and the free service has always served me well.

I guess its time I made a choice – or perhaps only being able to listen to songs 5 times will help to expand my musical vocabulary

Yesterday Google finally announced the release of a Google Docs app for Android.

It came with a few surprise like a cool widget for your homescreen and a really snazzy UI but the real big news was the introduction of OCR support.

Usefulness

Although I’m deeply entrenched in the Google-sphere (email, calendar, mobile OS, Picasa) I’ve never really embraced Google Docs. The introduction of this new app changes this.

I doubt very much that I will use the Google Docs app to really do any heavy duty word processing (yet) but for note taking, idea storage and project/task/action management its perfect.

At the moment I use a mixture of tools to achieve these processes – Dropbox, Evernote and Gmail are the main candidates but I can now see Google Docs replacing most these tools in some way (Evernote will most defiantly fade into obscurity) .

How does it fly?

To give the new OCR feature a trial run I decided to take a quick snap of some clearly printed text and see how the app performed:

This example is a page taken from the book ‘HTML5 for Web Designers‘ the text in the image is a little hard to read so here is a transcript of the most legible part:

Error handling might not be ofmucli interest to web designers, especially if we are writing valid. well-formed documents to begin With, but very imporkmt for browser makers. Whereas previous markup specifications were written for authors, HTML5 is written for authors and implementers. Bear that in mind when perusing the specíñcation. lt explains why the HTML5 specification is so big and why it seems to have been Written with a level of detail normally reserved for

Taken from ‘HTML5 for Web Designers‘ by Jeremy Keith

Now, I see you smirking but its not half bad! This was a first attempt in bad light on a bent page with pretty small text and you can make out most of it.

Not bad for a v1.0 release!

What’s missing?

Google Docs ain’t perfect, its missing a couple of key features on the web and app versions.

One thing that Evernote still has that trumps Google Docs is audio note taking. I love warbling into my phone at length and letting it store my ramblings in the cloud for later use – I’m pretty sure Google will trump this feature eventually as they have invested a LOT in audio to text conversion, its just a matter of time.

Finally, cloud storage is great, but I’d love to be able to sync to my desktop/device in a Dropbox-style fashion. I know this is against the Google-ethos but I can dream