Trainers Talk Tech

Over the past week, I have been surprised by the number of eMails and calls I have received from people in my network regarding HTML 5, Flash, Adobe and Apple. Folks in my eLearning circle are abuzz and asking questions about the future of Flash and the Web and what "these changes" are going to do to the field of eLearning development.

I am so over it.

I really, truly believe that right now, at this moment, it’s a non-issue. Initially, I was concerned because of Apple's childish decision (there, I've said it) not to include the Flash player on their iPad and iPhone. Then I started thinking about how my business was going to be impacted by the lack of Flash on these devices, and I had a huge "So what?" moment. So what if I can't run my stuff on iPads and iPhones? Are my business clients going to be negatively impacted because they cannot run "Effective eMails and You" on their iPad?

Odds are, I think that we won't see any kind of major investment into iPads at the corporate level. Why? Do you see IT teams making decisions to replace Blackberries with iPhones? Do you see IT teams issuing NetBooks to their employees instead of laptops and desktops? Is the iPad that much more powerful than a NetBook? Is the App store a blessing or a curse to an IT team concerned about privacy issues? If I issue my employee an iPad, do I dictate which apps are allowed to run? Who gets the app the employee purchased after termination? And on and on and on…in this climate, business have more important things to think about than jumping ship to a new technology infrastructure.

What about the business of HTML 5 killing Flash? Why are they mutually exclusive of each other? HTML 5 has a long, long way to go before the standards are finalized; generous estimates state that the standards will be in place in 5 years; conservative estimates consider 10 years a more realistic guess. Either way, this means that the web designer/programmer and eLearning designer/programmer is facing 5-10 years of pain because of the ultimate weak link: the browser.

HTML 5 is a programming language, but it is up to the browser to interpret that language and display the content. If the browser can't render the code, strange things start to happen in the display. We are facing that now with some versions of CSS. Different browsers on different platforms interpret the CSS differently and browsers display the content as they see fit. Look at sites on your Mac using Safari or Firefox and then on your PC using Internet Explorer - slight differences may appear if your programmer used CSS to any major degree.

Until HTML 5 gets standardized, each browser will interpret it differently. It's World Browser War III.

I have to tell you from experience (building on the web since 1996), clients don't get it and they don't care. If it works fine on your machine but breaks on the client machine, it’s broken. Clients don't want or appreciate long winded explanations of how browsers work; they paid you to design and program something and it doesn't work on their computer. You stink. It's a painful process of trial and error, multiple browser testing and all that stuff we used to HAVE to do during the previous World Brower Wars.

Adobe CTO says that they are going to make the best tools for HTML 5 and people scream "OMG!!! Adobe is saying that they are going to drop Flash!!!" No, it means that Adobe is going to keep current with browser coding tech and make their tools better by including it, just like they did with previous versions of HTML and with CSS. It's nothing to hoot about - it's a great step in the right direction. Adobe has always done this with Dreamweaver to ensure that coders have the most current tools at their fingertips. It’s great, and in no way says anything negative about Flash.

And while I am on that note, why is Flash suddenly Satan?

As far as I'm concerned, Flash is awesome. For me and my customers, it is the best way to deliver interactive content and eLearning for distribution over the web. Period.

Think about this: The odds are HUGE that the HTML 5 standard will still support browser plug-ins which means Flash will run just fine in HTML 5 standard browsers. Your current Flash movies and content will run in the HTML 5 standard browser, as long as that browser allows for the Flash plug-in. Based on the current specs (point 2.1.5), the use of plug-ins hasn’t gone away. Repeat after me – HTML 5 browsers will run your Flash projects.

Right now, the big whoopdy is Flash video vs. HTML 5's video capabilities. Sure, the browser will now be able to play video files, but what about the interactive capabilities of Flash? Will HTML 5 allow me to create the unique, interactive learning experiences that I build in Flash? Will HTML 5 allow me to store variables and convert them to numbers, compute on those numbers and then deliver customized responses based on those numbers? Will HTML 5 allow me to program “If...Then” paths based on user feedback and decision making? It doesn’t look like it.

Flash is a great tool and the files it creates display the same in every browser on every platform. The inconsistencies in the way the browser displays content has no impact on your .swf. It runs the same, it looks the same, it feels the same, and it sounds the same on each and every platform. It is a stable tech that my clients understand and provides me with creative flexibility. I don’t every have to say “no” to a client when building in Flash.

It needs to be stressed again that just because HTML 5 is coming out doesn't mean that Flash goes away. By the time HTML 5 standards are finalized, Adobe will have released Flash CS6, CS7, CS8 and maybe even CS9. Developers and the general public are freaking because Apple is ignoring the huge install base, the huge number of Flash developers and issues some sweeping statements against Flash. Since when is Apple the “be all, end all” of computing technology? If Apple says it, it must be the right?

In 2006, the W3C indicated an interest to participate in the development of HTML5 and in 2007 formed a working group chartered to work with the WHATWG on the development of the HTML5 specification. Odds are, you didn't know about it until Apple kicked Flash to the curb a month ago. I truly believe HTML 5 a long way off, will be filled with developer frustration as the browsers work on figuring out how to display the code, and it will not have the same multimedia and computational power I currently enjoy using Flash.

Clients don't always care about the technology, they just want it to look a certain way and to work as they want it to work. Until HTML 5 standards are finalized and all the browsers have figured out how to display the code, and until I can create the same multimedia/interactive experience for my learners, I'm going to continue developing my eLearning in Flash.