Flash is the technology, HTML5 is the adaptor.

I wanted to write down my thoughts upon reading the Smashing Magazine article on the gradual disappearance of Flash on the web. Along with the recent discussions rising from Apple’s moves on clearing Flash from the face of the earth, web and  iDevices, it stimulated many of us to think if HTML5 can really replace Flash.

Without drilling into technical details, I think holistically:

Flash (and Adobe as a company) had always been the graffiti guy of the leading technology for the web. It led the technology on the web.

HTML5 and CSS had always been the catching-up standardization officers. They adapted the technology.

Adobe always had the advantage of having Flash 99% compatible in all browsers and operating systems. Once they created the flash framework right, it was easier for them to build new technologies upon this framework, going forward with the convenience of high-level compatibility. Native 3D support, progressive video format, hardware (microphone,webcam) access, Augmented reality, etc. got eventually developed either by Adobe or 3rd party developers who Adobe always supported. Flash had always been a designer friendly environment, including visual designers not knowing actionscript but using basic timeline’d interface.  We saw amazing digital experiences created on the web, and Flash started being used for not only full-blown experiences but also partial sections on web pages (widgets, flyout navigations, slideshows).

Yes, HTML5 is great, in many cases providing similar experiences to Flash, and provides great flexibility for developers. I am excited to see it becoming the new standard. But it will never have the advantages of being a framework developed in-house as Flash. Biggest problem with HTML5 is still there because the rendering engines are various, and unfortunately behaving quite differently in complex designs. Although W3C is the school teacher, the students applying the language in the real world are Google, Apple, Microsoft, and couple of other browser developing companies. But most importantly,  it will not be possible for these companies to support 3rd party developers in rhyme with each other in the near feature, even if they get along well to establish the same standards and competitive speeds. As a developer, I will not be easily able to extend this language above the limits of what Chrome, Safari and IE provides me. I will not be facing one very open-minded company like Adobe, I will get stuck between the evil standards fight between Google, Safari, and Microsoft. While Adobe was trying to make sure Flash works at its best in all platforms, Safari will ignore when IE tries to bring new (now forgotten) features like web slices.

So, what’s going to happen Sinan?

Yes, basic and common features that are currently being served with Flash, such as video streaming, pixel level canvas drawing etc, will be replaced with HTML5. Though it is not because we hate Flash, it is because the support for Flash will decrease eventually by the similar unfriendly moves of the other platforms and browsers. But Flash will keep on leading the digital technology on the web (if Adobe keeps playing it right), and FWA will still be filled with many Flash driven websites. Safari on iPad will never be the “best browsing experience” without supporting Flash. Creatives of today’s world will never appreciate Apple forbidding 3rd party application development tools (such as Adobe CS5) for iDevices. HTML5 will only go this slow.