Q) What does YouTube, dubstep, and Reddit have in common?  A) This curve. 

If I were in charge of an advertising holding company, I would buy up as many content production houses as I could.  I would organize the content creation activities into systems that foster serendipitous discovery of new content, products, and services (read: the opposite of Google search).  This would include the embracing of new content standards, creation of new and enhanced consumption verticals, and a focus on providing useful, compelling, quality experiences within these verticals.  

The goal would be to provide advertising within these verticals in such as way as to have it actually complement the overall experience.  To avoid adding another needle to an ever increasing content haystack and instead to help sift through the hay.

Convergence - we’ve been talking about it for so long, I almost hesitate to bring it up again.  Here’s the story in a nutshell - Without your TV, convergence amounts to a hill of beans.  Apple has been on the cusp of creating a compelling version of convergence - and there have been glimmers of hope with Microsoft’s Xbox.  But the latest Apple TV has fallen short and it’s been almost a year since the Xbox 360 launched its integration with Netflix, Facebook, and Twitter.  The story of Xbox 360 and Apple TV can perhaps be similarly stated - Without the Web, convergence amounts to a hill of beans.

Now finally, I think we have a compelling vision of the future - with Google TV.

Of course, this isn’t a product review.  There are many better places for that. Ultimately, what I’m interested in is the interplay between broadcast content, web content, and applications.  And that’s where Google TV lives.  

On the surface, the whole thing might seem very familiar.  Even after watching the promo materials, (and before I had a chance to try it), I found myself thinking “haven’t we seen this before?”  I mean, hasn’t the “Web met TV” before?  You know… in a gadget called “Web TV?”  I have my own point of view about the whole web-on-tv experience…  in a past life, the fine folks at Web TV gave me device so I could optimize sites and evangelize the product.  From a developer’s perspective, I found Web TV interesting - but rendering was slow.  From a user’s perspective, without any true integration between Web content and TV content - who really wants a big keyboard on their couch?  

It’s easy to see why Web TV failed.  And at times Google TV can seem like Web TV all over again…  browsing can be slow at times, and the Logitech Revue does have a keyboard.  

But what’s striking is what Google TV gets right.  This isn’t just the Web on your TV. This is Google for your TV.  The first thing I did was a “Live TV” search… I Googled “ocean” and got a list of ocean-related content that was currently playing that I could immediately watch, and related content that would be playing in the future, which I could immediately DVR.  That mental model - the Google search model - replaces channel surfing and aids content discovery in a profound way. Shark week will never be the same.

The “Live TV” feature was great, but I decided to turn on a football game.  When the commercials came on, I opened up Google Chrome and watched the latest AOTS Around the Net segment, while still watching the game using picture-in-picture.  In fact, once the segment was over, I turned the game off, and browsed to Comedy Central to watch the latest Colbert Report.  And then to PBS Frontline just to see how other content might fare… everything worked great, and after accessing the vast content that is available from sites like PBS you get another idea of how this is different.  Much of the video content is clickable and interactive.  

In much of broadcast “interactive video” is thought of as a zero-sum game.  It brings up questions of who creates the specialized content, how would consumers access it (ie did it have any mass), and who would pay to produce it?  But with a TV that’s not just web-enabled, but web-friendly - interactive video is a natural and abundant alternative, even complimentary, source of entertainment.  Of course it is.  Yet, it’s a shift that can easily be downplayed, even while it is changing the nature of both how we watch TV and how we create TV content.

And I haven’t even mentioned the Android app platform or the coming TV app gold rush.  The installed apps (especially Pandora, Netflix) are great and, while there’s no app store currently, when you look at how apps are changing how we consume Internet content across mobile devices - it’s easy to imagine how much apps alone will change TV consumption. 

Google TV is a major milestone in a set of devices that will change how we consume TV.  If it’s allowed to, that is.  It’s clear any Web-on-TV device is going to have to navigate a whole range of issues brought by content providers and carriers.  It’s also clear that the stakes just got a lot higher.  Everyone wants a piece of the biggest screen in your house… the big question is how the pieces will be divided and if, after the feeding frenzy, there’ll be anything left for you.

—Sean

(photo by flickr.com/egarc2/2437521787)

Google Wave is such a complex tool that I hadn’t really considered that there might be a mobile version of it. With Google having such a robust web-based mobile offering, it seemed like a possibility, but given that Wave is only in preview release - and stretches the limits of a desktop browser - it seemed like a remote possibility at best. So, when I tried to access Google Wave on my iPhone, I found what I expected to find:

A roadblock telling me my browser wasn’t supported. Fair enough. But then I noticed the last line - “If you want to continue at your own peril, go ahead” - all but encouraging me to continue and see what folly awaits. Boy, was I surprised at what I found….

What loaded up was a fully-baked mobile UI. Pretty even, by mobile standards. Surely, none of this could work… preview release and all, it must be a mistake… a build that was released in error to be rolled back ASAP… so I clicked on a wave to test…

And the whole wave loaded up… well, except for the extensions. Truly, I don’t expect most Wave extensions to make the jump to mobile well, if at all. But the rest of the wave was there, playback controls included.

This wave’s extention was fully functional from the iPhone.

I could create a new wave…

And even comment on existing waves.

Honestly, I’m now more excited about the mobile version of Wave than the desktop version. Something about the mobile interface makes the whole concept of a wave more digestible and friendly. Sure, maybe all the extensions won’t work, and maybe the real-time execution on mobile will come across as a little less real-time…

The point is, Google clearly isn’t treating Wave on mobile devices as an afterthought. Which makes Wave even more of a game-changer than it already was.

QUICK UPDATE:

Further evidence that mobile Wave isn’t an afterthought:

When you bookmark Google Wave from Safari, you’ll see the above icon.

“What’s ubiquitous and cheap?” Varian asks. “Data.” And what is scarce? The analytic ability to utilize that data.