So I signed into TweetDeck for the first time in months today (sorry for missing all the @cartoonsmart tweets, I’ll try to work back on them ) In Tweetdeck I have a search column setup for Adobe related tweets, and I saw a frillion of links to this article titled Adobe: 7 Million iPhone users want Flash and that title about says it all. People want Flash. I was more interested in this quote:
According to Wired magazine, Apple’s CEO Steve Jobs recently claimed Adobe is lazy, Flash is buggy, and the future of the Internet will be HTML5 based anyway.
Well first, Steve Jobs has obviously been using a Mac for quite a while. And okay, often times Flash Player on the Mac IS buggy, lazy, and worse, even crashy. For a decade now, Windows machines have been displaying Flash content WAY better than the Mac. So Steve might want to check under the hood at some point and see why Flash isn’t running so well for him and the rest of us Mac folks.
Moving on, is HTML5 really going to be the future of the internet? Well I’ve seen some cool examples of what HTML5 can do, but I thunk to myself this morning, “what exactly can html5 do?”. So I went looking for some real examples that weren’t just Star Wars text scrolling back into space, and I found a good intro to Html5 from Brad Neuberg (a guy who works for Google)…
Its long and its paused at the moment because I’m still watching it, but from what I’ve seen so far, HTML5 is cool, but it clearly needs an easy dummy-friendly editor like what Dreamweaver does now for HTML . Lets face it, most folks don’t like writing code. Even easy code, like what I had to type out to get that Vimeo video embedded above. We want to push buttons that make stuff, or use brushes and paint can tools to create art. And watch our art on a timeline slide around to get an idea of timing, not hacking away with code. And considering all this talk in the video of animation possibilities, vector graphics, collision detection, mouse events, it seems like a better program for publishing HTML5 content wouldn’t be Dreamweaver but instead Flash.
So lets suppose we live in a world where Flash becomes the favored editor to export to HTML5. Which is quite likely considering Flash already exports to just about everything else imaginable, Swf, AIR, exe, projector, Quicktime, PNGs, JPGs, and soon even iPhone apps. Do you, the Flash developer, decide to embed your Flash-made content as a swf with the ever-changing proper HTML tags, or do you display your Flash-made content with the new HTML5 code? Well the determining factor would obviously be your audience. How many folks will see it or not see it based on whether you publish with Option 1 or Option 2. Duh, I’ll choose more people.
And development-wise your browser embed method is also a pretty minor choice. Us Flash developers spend 99.5% of our development time within the program creating, animating, etc, and very little time publishing and uploading. I could really care less about what html tags display my work. So in the end, devices like the iPad or the iPhone could play into that decision. But at the same time, HTML5 had better work. Overall Adobe has done a pretty great job of letting us Flash developers cram a ton of content into a swf, and play it mighty well. If HTML5 wants to be a playa, they better be able to handle doing what we wanna do…for starters, another classic Mario Bros emulation.