Two new HTML5 authoring tools

More than a year ago, I wrote a blog post bemoaning the lack of HTML5 authoring tools. Then as now, you could create sophisticated content using HTML5, CSS3 and JavaScript, but you had to hand-code everything. Now, we have beta versions of two different HTML5 authoring tools that promise to make the process a lot easier.

First, there's Sencha Animator, which focuses on CSS3 effects (transitions, animations, transforms, and anything else you can define in CSS3). It provides an interactive timeline for creating animations with keyframes. Next, Adobe announced the first preview version of Edge, its authoring tool for HTML5, CSS3 and JavaScript. Like Animator, Edge uses a timeline, but it's considerably more sophisticated: The user interface is designed to look and work similar to those of Flash Professional and After Effects, its animation framework is based on jQuery, it natively imports and exports HTML, CSS3 and JavaScript, and it stores all its animations in a separate JavaScript file rather than modifying the CSS3 file(s).

With Adobe jumping into HTML5, the obvious question is whether Edge is a replacement for Flash Professional? Not yet. Both Sencha Animator and Adobe Edge remind me of Swish Max4, an Australian authoring product that outputs Flash but is considerably simpler and easier to use than Flash Professional. Edge is still early in its development; when Adobe releases a new tool like this, it's typically a year away from commercial release. In addition, different browsers implement different portions of HTML5, and it will take time for the most popular browsers to fully implement the specification (which isn't even scheduled for ratification by the W3C until 2014). However, we're getting closer to the point where HTML5 becomes a viable replacement for Flash for a variety of applications.

Given that Adobe is cannibalizing itself with Edge, there's an obvious concern that the company might cripple Edge in order to keep Flash viable. If Adobe was the only company creating HTML5 tools, that would be a legitimate concern, but other companies are competing in the authoring tool space. If Edge creates inferior content, developers and artists will use a competing product. My belief is that Adobe would like nothing more than for Edge to make up for all the revenues that it's losing as Flash is abandoned, and that means that it can't create a second-rate authoring tool.

Adobe and Sencha are working to make HTML5 look and work more like Flash, and additional companies and organizations are inevitably going to release their own authoring tools. We may only be a few years away from witnessing Flash become a legacy application.

HTML5: The "Not Quite There" Valley

The battle between Apple and Adobe over Flash, which has been joined to a lesser extent by Microsoft and Opera, is almost certainly going to end with HTML5 as the dominant way of delivering video and interactive content on the web, with Flash becoming the RealMedia of a new generation. It'll be used by a few people, especially in legacy applications, but will fall out of mainstream use. However, that's not where we are now.

Today, Flash is still very much a mainstream technology, HTML5-compliant browsers implement different portions of the standard, and HTML5 itself continues to evolve. There are no graphic authoring tools capable of creating anything coming close to Flash-based interactive content in HTML5. Yesterday, Scribd announced that it's starting to shift from Flash to HTML5 for its online document sharing platform, after a six-month development effort. Moving from Flash to HTML5 for video is now fairly easy, but for interactive content, a major development effort is usually required.

So we're still far away from the time that HTML5 will be ready to take over for all of Flash's applications, and the decision tree is now very clear: If you need to access Flash content or applications, forget about using any device that runs on the iPhone operating system. Once Adobe releases Flash 10.1 for Android, that won't be such a big obstacle. If you're developing applications that need to live for more than a year or two, however, you should seriously consider wading into the HTML5 pond now to avoid having to rebuild all your code for HTML5 later on.

H.264 now comprises 66% of encoding.com's videos

In response to Steve Jobs' open letter about Flash last week, TechCrunch contacted encoding.com, a video encoding service, to get their statistics on what formats their clients are requesting. In Q1 2010, 66% of all videos that encoding.com processed were encoded into H.264, while On2 VP6 and .FLV (which could be any codec supported by Flash, but in this case probably means Sorenson) together add up to 26%. (Ogg Theora is barely 2%.) Here's the chart:

Keep in mind that encoding.com has encoded 5 million videos over the past year for a variety of clients, but it in no way represents the majority of video sites or content. Also, these numbers represent new or transcoded files, not the huge number of legacy video files that still exist on the web. Nevertheless, encoding.com's numbers suggest that H.264 has got major adoption momentum. However, that could change.

Google's rumored announcement later this month that it will make On2's VP8 format available as open source may change the balance, especially if YouTube starts encoding its videos in VP8. According to ComScore's traffic numbers for March, YouTube had more video viewing traffic than then next ten sites put together, so as YouTube goes, so goes a large part of the market.

Is Microsoft working on HTML5 design tools?

A few weeks ago, I wrote a post asking where the tools are that will allow mere mortals to write HTML5 that works like Adobe's Flash. Adobe has Dreamweaver, but it has a strong incentive to keep developers and users from migrating from Flash to HTML5. Microsoft has the Expression suite, but it also has Silverlight, so I thought that it wouldn't take up the challenge, either.

Yesterday, however, a Microsoft executive went on the record stating, and I quote, "The future of the Web is HTML5." That quote came from Dean Hachamovitch, Microsoft's General Manager for Internet Explorer, and although he was writing about web video, his comments can easily be seen as extending beyond just video.

It would make a lot of sense for Microsoft to go "all out" for HTML5 support, not just in IE but in its Expression Studio authoring tools as well. Silverlight has miniscule market share compared to Flash, so Microsoft could cannibalize Silverlight without hurting its revenues. Further, by making Expression Web a better HTML5 graphical development tool than Dreamweaver, it could steal market share from both Dreamweaver and Flash.

Adobe is vulnerable, and no one smells blood in the water better than Microsoft. Expression Studio 4 could be Microsoft's opportunity to leapfrog at least some components in Adobe's Creative Suite 5. Microsoft can offer Silverlight for those developers who want it, and to provide capabilities that won't be implemented in HTML5 for some time, but it doesn't need to protect Silverlight the same way that Adobe needs to protect Flash.

Steve Jobs goes on the record about Flash

Apple's position on Adobe's Flash is well-known, from the company's new iPhone Developer Agreement, Steve Jobs' remarks at an Apple "Town Hall" meeting, and a series of emails between an iPhone developer and Jobs. However, Jobs has now gone "on the record" with an open letter explaining Apple's decisions.

I've linked to the open letter so you can read it yourself, but here are the key arguments:

1. Despite Adobe's claims of openness, Flash is a proprietary platform and format controlled by Adobe. Apple's approach is to use HTML5, CSS and JavaScript, all of which are open industry standards controlled by standards committees.
   
2. Adobe claims that 75% of the video on the Web is in Flash format, but an increasing number of sites (including YouTube) also supply video in H.264 format that iPhone OS-compatible devices can use, so the problem is getting smaller every day. Jobs admits that Flash games won't run on iPhone OS, but there are over 50,000 games and entertainment titles already available for the iPhone, so the lack of Flash hasn't caused a problem.
   
3. Flash is the number one reason that Macs crash, and Symantec has reported that Flash had one of the worst security records in 2009. Flash doesn't perform well on mobile devices, and Adobe has been promising to deliver a full version of Flash for mobile devices for almost two years and still hasn't shipped. Apple doesn't want to subject iPhone OS users to these problems.
   
4. Most Flash video uses a Sorenson or On2 codec that requires software decompression, while H.264 can use hardware decompression. In Apple's tests, videos that can use H.264 hardware decompression play for 10 hours on an iPhone before the battery runs out, while viewing videos that require software decompression cuts battery life in half.
   
5. Flash was designed for keyboard and mouse interfaces, not touch, and the iPhone, iPod touch and iPad rely on touch.
   
6. Cross-platform development tools like Flash can't take advantage of new features as quickly as Apple rolls them out, so Flash developers can only use these features after Adobe supports them. Also, cross-platform tools encourage development of  "lowest common denominator" applications.

You may disagree with some of Jobs' arguments, but his open letter is the most comprehensive and clearest presentation I've seen of why Apple has decided not to support Flash.

Flash: It ain't dead yet

Tonight, TiVo announced its new Series 4 DVRs, called Premiere and Premiere XL, which will ship next month. Engadget covered the announcement in New York, so I'll skip the product details. However, one of the most intriguing aspects of the announcement is that the Premiere's user interface is built on Flash, and its performance looked quite smooth. While Apple and Adobe are throwing spitballs at each other over Flash on the iPad, TiVo has just moved Flash front-and-center into the living room. It remains to be seen whether the Premiere will halt TiVo's slide in the DVR business, but at least it indicates that the company isn't giving up on the hardware business.

Hulu Part 2: At war with everybody

Paul Yanez, a talented developer who had previously written a clone of Joost as a Flash application, recently released a program called MyMediaPlayer to provide a desktop interface for Hulu. This app uses Hulu's published, public specifications for accessing and displaying videos. It uses the Hulu player, doesn't strip out any advertising, doesn't introduce any advertising of its own and is free. Nevertheless, Hulu has repeatedly come up with ways to block MyMediaPlayer, and it appears that after five rounds of reworking the application in order to get it working again, Mr. Yanez has given up.

In the same vein, Boxee was able to reestablish support for Hulu by connecting to that company's RSS feeds, the same feeds used by Internet Explorer, Firefox and Safari. Nevertheless, in just a few hours, Hulu blocked Boxee's access to its RSS feeds. As I write this, Boxee claims that it has worked around Hulu's changes and can again access the RSS feeds. Perhaps the best thing that Boxee could do is to change its browser user agent to look like Internet Explorer, so that Hulu would have to effectively shut down the RSS feed to block Boxee.

I don't know why Hulu is doing this, but it's only making itself look idiotic. All of its blocks will eventually be worked around, and its content isn't so precious that it's only available in one place. As I've written before, its actions are encouraging, rather than discouraging, piracy. Every time I see one of its commercials, I see a company that doesn't get it trying to act cool. Perhaps the people who called the company "ClownCo" weren't wrong, just premature.

A big win for Silverlight--from the last place you'd expect

Microsoft's Silverlight has played a poor runner-up to Adobe's Flash in terms of player installation and usage ever since it was introduced, even with Silverlight powering NBC's Olympics video last summer. Today, however, Silverlight got another big win, and it's not something that will last for only two weeks. According to Engadget, Netflix just announced that it will finally bring its "Watch Instantly" streaming video service to the Mac, using Silverlight. One reason that Netflix went for Silverlight over Flash is Microsoft's Digital Rights Management platform, called Play Ready. I suspect that another reason is that Microsoft doesn't charge for players or servers, while Adobe still charges quite a bit of money for servers. Having Microsoft software as the preferred streaming platform for Macs is a bit of a shocker, but it apparently makes both business and technical sense for Netflix.