November 22, 2010

So, what has Adobe actually done for HTML5 lately?

Oh, y’know, only little bits here and there. :-)  Here’s a quick recap from just the last ~6 months. I’ve bolded/italicized the bits I find most interesting.

 

• New authoring support shipping now:
  1. Shipped the Dreamweaver CS5 HTML5 pack, facilitating multiscreen work
  2. Shipped the Illustrator CS5 HTML5 pack, enhancing CSS & SVG export
  3. Added support for using HTML5 content in digital publications
  4. Added support for Firebug, Safari 5, and more to BrowserLab
  5. HTML5 Video:
     1. Facilitated the use of HTML5-tagged (non-Flash) video in Dreamweaver
     2. Added HTML5 video publishing to the Scene7 hosted service
     3. Added HTML5/Flash support to the Open Source Media Framework

      
• Future authoring tools:
  1. Demonstrated a prototype tool for creating HTML animations & interactivity
  2. Demonstrated technology for converting Flash graphics and animation to HTML5
  3. Announced a new tool for creating HTML without coding

   
• Supporting community technology:
  1. Working to contribute advanced typographical layout code to WebKit
  2. Actively contributing to jQuery Mobile (which leverages HTML5 & CSS3)

   
• Miscellaneous:
  1. Added HTML5 slideshows to Photoshop.com, in parallel with Flash
  2. Added HTML5 video playback for videos hosted on Photoshop.com; Adobe TV to follow
  3. Embedded WebKit in CS5 apps to facilitate HTML-based extensibility
  4. Added HTML5 compatibility tracking (NetAverages) to CS Live
  5. Began offering typefaces via TypeKit

 

This isn’t about one technology (HTML, Flash) “vs.” another; it’s about putting customers, and the solutions to their problems, ahead of any technology.

So, let’s stick a fork in the “Adobe doesn’t like/doesn’t support HTML5″ canard once and for all. Can I get an amen? [Update: If that war of perception is truly over, fantastic. As I say, I'd be delighted to lay it to rest.]