Archive for March, 2011

Comb Over Charlie vs the Web-Beacon’d Pundits of Doom

Short video worth watching… single game running across multiple screens… more info from Charlie Schulze and Jens Loeffler.

Simple story — delivering to a new form of device should require minimal redrawing/layout/interaction work, and delivering to a new brand of device should require even less work than that. It’s still early days, but Charlie’s experience shows that this is a reasonable and attainable goal.

Is this the story in the popular press? No… the goal of techpress is to earn revenue, and attracting the clicks is the main need. They don’t disclose their private communications with companies, and feature pseudonymous comments which could well be from marketing-agency personas. When they write of privacy their own pages will usually call assets from Google, Facebook, and other cross-site trackers. Even when the New York Times writes of a superquake and mega-tsunami in Japan, they’ll sensationalize the nuclear angle despite all science to the contrary. The chattering-class is often offbase in what they choose to discuss.

Please take a look at the video yourself. That cross-device delivery is the way things should be, and is increasingly the way things really are. And in the end, this reality will trump lame talk.

Recent news, steady progress

Funny news day — lots of little things popping, some drawing much more attention than others, hard to get perspective. There’s a common theme among them, however. Even though there’s lots of growth in new types of environments, there’s a lot of work in bridging them, too.

One example is how browsers are starting to expose Flash Player local storage… from the FAQ:

“Integration with browser privacy controls for managing local storage — Users now have a simpler way to clear local storage from the browser settings interface, similar to how users clear their browser cookies today. Flash Player 10.3 integrates control of local storage with the browser’s privacy settings in Mozilla Firefox 4, Microsoft Internet Explorer 8 and higher, and future releases of Apple Safari and Google Chrome.”

Letting webpages store more-than-cookie-sized data is a good idea, as recent HTML5 local-storage work shows. But as cross-site tracking and personality databases become more worrisome, it makes sense to expose integrated local-storage to public control however people wish to control it. The good news is that different parties can (and do) work together to bring this about. Progress.

Another example is the Wallaby project… not as dramatic as Techmeme may paint it, but it’s still useful to be able to bring basic SWF assets into a different delivery environment. Fragmentation is natural during fast evolution, but connecting such silos is natural too. Progress.

A subtler example is from the Dreamweaver team this week, about the differences in touch events across different WebKit-based browsers. Touchscreens and scrolling forms, or preventing doubled events when there’s also a trackball controller… natural for fragmentation to occur, and natural to bridge that fragmentation too.

More obvious is the work that Adobe’s Digital Publishing group has been doing… working with major publishers to bridge across all the various islands of new devices rapidly appearing. This will soon help smaller publishers too.

Screaming headlines may clash and obscure significa, but the real pattern underlaying the news is easier to see: we’re rapidly gaining a wide variety of connected digital screens, and the big work is in helping anyone to write to them. There’s daily, incremental progress towards that goal… connecting those silos, bridging those islands.

Is video so hard?

The VIDEO tag isn’t as hard to understand as media campaigning would have you believe.

A good example is at TechCrunch today: “MeFeedia Reports 63 Percent Of Web Video Is HTML5-Friendly”. Back in May 2010 the same TechCrunch writer wrote “H.264 Already Won — Makes Up 66 Percent Of Web Videos”. This in itself is pretty confusing…. ;-)

The background is that an encoding site measured what codecs their clients desire, then equated the popularity of H.264 (and any VP3/VP8) with “HTML5″, which advocacy sites then equated with “iPad”.

The presence of an H.264-encoded video does not mean the site has a VIDEO tag to invoke it… retagging a site and providing a control UI does not come automatically with video compression. The numbers, as presented, mean nothing. But the headlines have already attracted further confusion, with weak headlines like “Apple Won The War Against Flash”.

My October post “Who Needs War?” still contains background on how video works, and the title was a soft allusion to those who need to posit some form of conflict to justify their position. Mike Chambers also explained how these basic technical aspects are being misrepresented.

There are so many blindspots and contradictions with this persuasion campaign. Take a look at, and their maps of popular browsers across the world. Firefox is the biggest “HTML5″ desktop browser, yet doesn’t decode H.264 video. Opera is the biggest “HTML5″ mobile browser, yet also doesn’t do VIDEO/H.264. Apple is just one small part of the total “HTML5 VIDEO” discussion. H.264 != “HTML5″ != Apple.

More confusion: “The choices between Flash, H.264, Ogg, and VP8 means that if a video publisher wants full user support (and they should), they’ll need to support several formats for each video.”

Makes no sense. Adobe Flash Player has used H.264 for three-and-a-half years now, reaching +80% consumer support within six months. There is no “choice between H.264 and Flash”, just as there’s no real comparison between your groceries and their shopping cart. One contains the other. This is very simple to understand.

In the real world, to show video to everyone, you need Flash, and then something for Apple devices. Doesn’t require re-encoding the video, just re-working the site. Maybe provide something for older devices too.

And to understand the real world, do we need techblogs? The evidence they’re giving doesn’t lend confidence….