Last week we did a post on HTML5 and the affect it’s going to have on Adobe. Well this seemed to stir the pot in the office amongst the flash developers and the front end developers. The argument last week was pointing the finger at Adobe for not being standard compliant and fighting a lost cause with Apple. So this week we’re going to argue the other side of the fence and stick up for Adobe for developing a way to deliver interactive content.
HTML5 has a while before it actually becomes standard and adopted by all. Adobe has given the design community a way to visually create interactive content through is program Flash Professional. HTML5 does not give a visual representation other than the browser which in turn could take forever testing unless you know exactly what you’re doing. With Flash Professional you have your creation right in front of you in one program making your workflow easier to manage. Flash is still a pain to use unless you know what you’re doing, but easier to teach yourself and learn. With HTML5 you need to know HTML, CSS, and JavaScript to create what you want.
A big plus to Flash is it gives you a good visual/wysiwyg canvas to web develop interactive content. Instead of having to have your favorite editor open along with the browser and whatever other tools you use for web development, you have just one window with everything you need. That is where my idea to have an HTML5 export option in Flash comes in.
Also, I talked about how much a CPU hog Flash is compared to HTML5. On the Windows platform Flash isn’t as much of a CPU hog as it is on the Mac OSX platform. The reason for that isn’t because of Adobe; rather it’s caused by Apple not allowing the Flash Player to access certain APIs to the GPU accelerator on the Mac OSX platform. So, Apple is actually sabotaging the Flash Player on its desktop OS. As far as the iPhone is concerned, Apple has said Flash is a battery hog and from my experience owning an Android phone, it most definitely is. Reports have shown that Flash is better than HTML5 on a Windows PC and the opposite on the Mac platform. The only reason is that Safari uses the H.264 codec for running videos. Below are two emails arguing both cases and why one is better than the other.
Email:
“Given that HTML5 is only available in (some) of the newest browsers, I don’t find it likely that this will become a standard anytime soon (nor CSS3, etc.). It has a long way to go to catch up with the ~98% of internet users that already have Flash Player plug-ins. If you think about the large majority of users that are still using IE6, how long do you think it will be until 98% of the users have HTML5 capable browsers? Adobe has always been WAY ahead of anyone else in the field, and by time HTML5 is fully adopted (probably another 5-10 years), I am pretty sure Adobe will be above and beyond standards.
Flash wasn’t designed specifically for video (YouTube, etc.). Go to www.thefwa.com and try producing anything listed on there with standards (ain’t gonna happen). The idea of an HTML5 export would be awesome, but what it comes down to is that HTML5 cannot do everything Flash can.
And Apple is pretty arrogant in their decision to kill Adobe’s exporter support right before the launch of CS5, as many agree. I don’t think their intent has as much to do with standards as it does with control. I don’t think we’ll see Chrome or Firefox killing Flash support just because they are HTML5 compliant.”
Response to the Email:
“Once IE9 comes out every modern browser will support HTML5. Even IE8 supports some HTML5. Yes it will probably be a while before HTML5 becomes standard, but as HTML in general evolves, it will become standard, just like XHTML. The same goes for CSS3. I’m not saying that browsers will not support Flash entirely or that Flash is made for video only. What I am saying is that the more HTML5 evolves and the more browsers support HTML5, the less and less you’re going to see interactive Flash content. Flash is a CPU hog on all platforms, it may be less of a hog on one verses another but it’s still bogs down CPU power more than HTML5. I have seen the site you referenced before and there really isn’t much on that site I would think couldn’t be recreated with HTML5. Take a look at some of these HTML5 canvas examples http://www.phpguru.org/static/html5-canvas-examples. This will show how HTML5 can affect flash from an interactive standpoint. I don’t think Apple is being arrogant; they are trying to help evolve the web and adopt new technologies. HTML5 is more accessible across all devices and platforms and that is what Apple is trying to get across; making content accessible on everything. Yes, we have a while before IE6 is dead and everyone upgrades to IE9 but that doesn’t mean we have to stay in the stone ages until Microsoft realizes they don’t need to keep supporting a crippling browser.”
Despite our differences, we’re still friends and nobody got hurt. Every designer and developer has their own opinion on what should be standard and what is better.