- April 12th, 2010
- 348 Comments
In the current landscape of technology and accessing the Internet through devices such as picture frames, netbooks, cell phones and televisions, the benefits of Web standards outweigh those of Flash, especially when delivering content to a broad audience on various devices.
Flash is a proprietary product that sits on top of the browser to extend functionality. While Flash may have provided missing functionality for some time, it brings little value to modern browsers. As more and more designers and developers realize the benefits of Web standards and start using some of the features of HTML5 and CSS3, we’ll see fewer Flash-driven websites.
The Great Flash vs. Web Standards Debate
Advocates have evangelized Web standards for over 10 years. The debate among developers and designers often gets as heated as the discussion on same-sex marriage, causing uncomfortable divisions among some of the smartest people in the field.
With the recent announcement of iPad’s lack of Flash support and the continued lack of it on the iPhone, the debate has reached beyond the development community to include Adobe and Apple themselves. With Apple’s anti-Flash stance, it has become too hard to argue for a completely Flash-based website when it would leave out a potentially large audience.
Eventually, Flash will make it to mobile devices (250 million devices are expected to have full support by the end of 20121), but that’s really only a small part of the debate and one of the better arguments that Web standards advocates have.
At the heart of the matter is how to deliver a great experience to users no matter the technology or platform.
“HTML5 vs. Flash” is the wrong discussion. “Accessible rich media” is the right one.
In the end, we’re all just trying to create websites that can be accessed and used, regardless of the tools we use to deliver them.
Flash saw great success early on and pushed forward quickly. The small app that once mainly made animations quickly became a worthy development environment in its own right. Developers and designers alike chose to concentrate their efforts in that area, often segregating themselves from the open Web and backing the proprietary technology. Flash websites took over the Web, and Web standards didn’t allow developers to create the experiences that users were starting to expect.
Web standards may have fallen behind once, but they continued to be pushed forward by practitioners and those willing to embrace the idea of an open Web.
Web Standards: Benefits And Reasons For Adoption
The line between websites developed with Flash and Web standards has become blurred. At first glance, even the savviest developer would have a hard time discerning which technology was used for a website without peeking at the source.
The list of websites that are ditching Flash in favor of Web standards is growing every day. Even if these decisions are driven by the iPad and iPhone’s lack of Flash, they’ll soon reap the other benefits that Web standards bring.
Video has been an important step in moving Web standards forward. Video is one of the few things that could once only be delivered in Flash. The biggest leap so far has been YouTube5‘s adoption of the HTML5 video element (albeit in beta), allowing modern browsers to bypass the Flash plug-in and use video native to the browser’s player.
HTML5 video has encountered controversy (thanks to the current codec debacle6) and reports of unimpressive performance, but these issues will be worked out. Website developers will implement HTML5 video and choose an appropriate codec. When the biggest websites make this decision, we’ll end up with a de facto standard that gives browsers improved performance.
Modern Browser Adoption
HTML5 and CSS3 represent a great effort to advance native browser performance, and many browser providers are already implementing their specifications, even through they haven’t been set in stone. We have a lot to look forward to with CSS animation, canvas, local storage, geo-location and other specifications that will bring Web standards into a new era.
Although it will be many years before we see 100% of the emerging specifications implemented in browsers and see a large majority of users upgrade to those browsers, if we embrace the progressive enhancement of content, we’re well on our way to pushing adoption among developers.
Learning to produce progressively enhanced content, giving up pixel-perfect rendering in every browser, and embracing graceful degradation in older browsers can free up time to concentrate on other areas of development, such as accessibility and platform-delivery agnosticism.
Designing with progressive enhancement in mind and building from the ground up require designers and developers to think more about the infrastructure of a website, and this typically exposes the kinds of issues that arise when working from the top down (i.e. designing a website and then considering the fall-back).
Smart Phone Browsers and Context Delivery
The mobile Web is still in its infancy and usually an afterthought in the design process, but standard-based designs can degrade as nicely on phones as they do on older desktop browsers. In the absence of the Flash plug-in, a website can still deliver an exceptional experience without much extra effort (which would be cumbersome with a Flash website).
Mobile Web browsing is increasing exponentially, and ignoring these users is unwise. Web standards are the only option to deliver richer interactions in mobile browsers.
Web standards being what they are (i.e. standard agreement on the way code is constructed and served), user agents and scripts from outside a website can be written to access data directly from the HTML. Search engines, microformats, feeds, translation and bookmarklets all work because of the open nature and consistency between the data.
If we want the Web to be truly scalable and interconnected, then microformats and microdata and APIs for content might be just the answer. Otherwise, we’ll remain in the same position we were years ago when websites erected walls around their content.
Many people believe that the technology behind the Internet should be open and not competitive as it has been in the past. People should be free to consume and create information, without being tied down to the kind licensing restrictions and legalities seen with the likes of Flash, Silverlight and other corporately owned technologies.
Creating and delivering content with Web standards not only is the best technological solution but supports the freedom of an open Web.
Flash Does, And Will Continue To Do, Many Things Well
Just because Flash-driven websites are gradually disappearing doesn’t mean that Flash will disappear altogether. Too much content and infrastructure have been set up to magically vanish. Without vast restructuring or realigning of organizations and processes, plenty of Flash developers will continue to be employed, and plenty of Flash advertising will be directed at those ready to ignore it.
We owe a lot to Flash for making the Web what it is today, and it deserves that credit. Even though it showed less potential compared to the other plug-in technologies, such as Java applets, that emerged early on, it had a nice balance between seamless delivery to users and ease of development and deployment. Many other Web technologies, such as VRML and SVG, have tried to overcome Flash’s hold on the Web but have continually fallen short.
Where would the Internet be without Flash and the innovations it brought?
Ease of Use
Out of the gate, Flash was intuitive and easy-to-use application for both designers and developers, delivering the simplest of animations, yet able to scale to serve complex applications.
Because of its ease of use, Flash posed a lower barrier to entry for budding designers and developers. And combined with the suite of applications from Adobe, Flash fits well in the designer’s workflow.
You can’t argue with the fact that for many years Flash has been the only way to deliver rich interaction in a consistent way across a wide range of platforms and browsers. It’s still the only way to deliver video and audio to older browsers, and it will retain its throne for several more years.
If you’re a stickler for fonts and demand special ones for your website, then you’ll be saddened by the current state of font support in the browser. This shortcoming will have to be compensated by Flash and swfObject10 until
@font-face and various font formats become more widely supported.
Standards Not Quite There
As much as Web standards have advanced, we’re often stuck having to support older browsers in which Flash may be the only way to deliver audio, video and complex data-heavy interfaces. Thanks to early adopting Web browser providers, we can start using the HTML5 audio and video tag today. But we still have to plan for a Flash fall-back to deliver media in older browsers.
The same could be said for the canvas element for delivering complex visualization, 3-D animation and games. If a browser like IE6 needs to be supported, providing a decent fall-back for the canvas element can be complicated. Flash might just be the best choice for development in such cases. As always, your current and potential audience should determine your direction.
Progressively Enhanced Flash and Flash Injection
The best Flash developers take the same approach as the Web standards crowd, using Flash as a layer to enhance their websites and applications. If that continues, Flash will continue to have a place in delivering a great experience, serving mobile devices and reaching search engines and other user agent technologies. The Flash injection technique11 is the easiest way to meld the best of both worlds.
The Future of Flash
Adobe has never been the type of company to let a product stagnate. You can be sure it will keep pushing to get Flash on as many mobile devices as possible.
With Creative Suite 5, developers will be able to output Flash projects as native iPhone applications using the iPhone Packager13. And Flash could soon evolve from its early roots as an animation application to a full-fledged desktop and mobile application development environment with the help of AIR14 and related advancements (AIR might reach the mobile space pretty quickly).
Flash developers will likely be in even greater demand, as the demand to deliver applications consistently between desktop and mobile devices increase—even if they aren’t asked to create run-of-the-mill websites.
Web standards and Flash (and other plug-in technologies) are simply tools to create content for the Web. Even if Flash is on the decline for websites, Flash developers have no reason to worry about becoming obsolete.
Everything that is true for creating rich Internet applications holds true for whatever other tool you use, and transitioning to Web standards development may be easier than you think.
Flash and Web standards developers have more in common than they don’t. Interface and interaction design, typography, layout, graphic design and object-oriented programming are all still valid and important for both technologies.
Developers on both sides of the spectrum struggle with many of the same issues. They both set out to create a great user experience, to design intuitive interactions and to make websites easy for users. All of this is done not by the technology itself but by the people behind it.
Standards-Based Websites That Shine
Here are some examples of websites that have embraced Web standards and offer rich interaction. If you want to keep up with current trends, many great standards-based websites are featured on showcase websites such as NotCoffee16 and jQuery Style17.
Websites From The (Near) Future
Here are some “experimental” websites that demonstrate what’s becoming possible with Web standards. Be warned: these might work only in the most modern of browsers. To keep up with emerging standards-based websites, check out CanvasDemos62 and Chrome Experiments63.
HTML vs. Flash Resources
Here are a few fairly recent articles. Make sure to check out their comments.
- Flash, iPad, Standards96, Ahem97, by Jeffrey Zeldman
- HTML vs. Flash: Can a Turf War Be Avoided?98, by CNet
- HTML5 vs. Flash99, HTML5 Spells Death to Flash?100, by Remy Sharp
- Flash Is Dead! Long Live Flash!101, by Jeff Lamarche
- Flash Corporate Websites Are Dead… Oh, and Intros, Too102, by Xiik
- Is the Flash-Powered Agency Site Obsolete?103, by AdFreak
- HTML5 and the Future of Flash104, by Gartner
- Flash and Standards: The Cold War of the Web105, by Dan Mill of A List Apart
- Mozilla Warns of Flash and Silverlight “Agenda”106, by ZDNet
- 1 http://www.tgdaily.com/mobility-features/48439-adobe-touts-flash-101-at-mobile-world-congress
- 2 http://twitter.com/zeldman/status/8872227072
- 3 http://www.flickr.com/photos/erikcharlton/318019677/
- 4 http://www.flickr.com/photos/soldiersmediacenter/2887687406/
- 5 http://www.youtube.com/html5
- 6 http://arstechnica.com/open-source/news/2009/07/decoding-the-html-5-video-codec-debate.ars
- 7 http://unobtrusify.com
- 8 http://www.flickr.com/photos/virtualsugar/316200555/
- 9 http://www.flickr.com/photos/ejk/417437288/
- 10 http://code.google.com/p/swfobject/
- 11 http://www.alistapart.com/articles/semanticflash/
- 12 http://commons.wikimedia.org/wiki/File:Lasershow_Halifax_20070610.jpg
- 13 http://labs.adobe.com/technologies/flashcs5/appsfor_iphone/
- 14 http://www.adobe.com/devnet/devices/demos/
- 15 http://www.flickr.com/photos/63294897@N00/626148737
- 16 http://notcoffee.net/
- 17 http://jquerystyle.com/
- 18 http://www.pigeonandpigeonette.com/
- 19 http://www.pigeonandpigeonette.com/
- 20 http://www.goodworksmedia.com/
- 21 http://www.goodworksmedia.com/
- 22 http://madebyelephant.com/
- 23 http://madebyelephant.com/
- 24 http://euna.com.ar/
- 25 http://translate.google.com/translate?hl=en&sl=es&tl=en&u=http://euna.com.ar/
- 26 http://euna.com.ar/
- 27 http://www.artopod.se/kontakt/
- 28 http://translate.google.com/translate?hl=en&sl=sv&tl=en&u=http://www.artopod.se/kontakt/
- 29 http://www.artopod.se/kontakt/
- 30 http://www.dreamerlines.lv/
- 31 http://www.dreamerlines.lv/
- 32 http://www.serialcut.com/
- 33 http://www.serialcut.com/
- 34 http://u2.alfabank.ru/
- 35 http://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http://u2.alfabank.ru
- 36 http://u2.alfabank.ru/
- 37 http://www.arcinspirations.com/kobe/
- 38 http://www.arcinspirations.com/kobe/
- 39 http://unowhy.com/
- 40 http://translate.google.com/translate?hl=en&sl=fr&tl=en&u=http://www.unowhy.com/
- 41 http://unowhy.com/
- 42 http://cpeople.ru/
- 43 http://cpeople.ru/
- 44 http://www.worldofmerix.com/
- 45 http://www.worldofmerix.com/
- 46 http://www.thesixtyone.com/
- 47 http://www.thesixtyone.com/
- 48 http://bonadiesarchitect.com/
- 49 http://bonadiesarchitect.com/
- 50 http://www.pauljnoble.com/index.html
- 51 http://www.pauljnoble.com/index.html
- 52 http://www.adultswim.com/shows/index.html
- 53 http://www.adultswim.com/shows/index.html
- 54 http://glyde.com/
- 55 http://glyde.com/
- 56 http://alexarts.ru/en/index.html
- 57 http://alexarts.ru/en/index.html
- 58 http://adamrix.com/
- 59 http://adamrix.com/
- 60 http://www.ericj.se/
- 61 http://www.ericj.se/
- 62 http://www.canvasdemos.com/
- 63 http://www.chromeexperiments.com/
- 64 https://bespin.mozillalabs.com/
- 65 https://bespin.mozillalabs.com/
- 66 http://mugtug.com/sketchpad/
- 67 http://mugtug.com/sketchpad/
- 68 http://www.nihilogic.dk/labs/wolf/
- 69 http://blog.nihilogic.dk/
- 70 http://www.nihilogic.dk/labs/wolf/
- 71 http://www.disegnocentell.com.ar/ejemplos/transform/lab.php
- 72 http://www.disegnocentell.com.ar/
- 73 http://www.disegnocentell.com.ar/ejemplos/transform/lab.php
- 74 http://cs.helsinki.fi/u/ilmarihe/canvas_animation_demo/mozcampeu09_go_faster.html
- 75 http://cs.helsinki.fi/u/ilmarihe/canvas_animation_demo/mozcampeu09_go_faster.html
- 76 http://9elements.com/io/projects/html5/canvas/
- 77 http://9elements.com/
- 78 http://9elements.com/io/projects/html5/canvas/
- 79 http://www.chromeexperiments.com/detail/ball-pool/
- 80 http://www.chromeexperiments.com/detail/ball-pool/
- 81 http://people.mozilla.com/~prouget/demos/DynamicContentInjection
- 82 http://people.mozilla.com/~prouget/
- 83 http://people.mozilla.com/~prouget/demos/DynamicContentInjection
- 84 http://onecm.com/projects/canopy/
- 85 http://onecm.com/projects/canopy/
- 86 http://code.edspencer.net/Bean/index.html
- 87 http://code.edspencer.net/Bean/index.html
- 88 http://deanm.github.com/pre3d/colorscube.html
- 89 http://deanm.github.com/pre3d/colorscube.html
- 90 http://antscape.byethost8.com/bike/
- 91 http://antscape.byethost8.com/bike/
- 92 http://www.mattryall.net/demo/atlassian-vis/comments/
- 93 http://www.mattryall.net/
- 94 http://processingjs.org/
- 95 http://www.mattryall.net/demo/atlassian-vis/comments/
- 96 http://www.zeldman.com/2010/02/01/flash-ipad-standards/
- 97 http://www.zeldman.com/2010/02/03/ahem/
- 98 http://news.cnet.com/8301-30685_3-20000037-264.html?tag=fbshare
- 99 http://remysharp.com/2010/02/08/html5-vs-flash/
- 100 http://remysharp.com/2009/05/28/html5-spell-death-to-flash/
- 101 http://iphonedevelopment.blogspot.com/2009/08/flash-is-dead-long-live-flash.html
- 102 http://xiikblog.com/2009/01/19/flash-corporate-websites-are-deadohand-intros-too/
- 103 http://adweek.blogs.com/adfreak/2009/04/is-the-flashpowered-agency-site-obsolete.html
- 104 http://blogs.gartner.com/ray_valdes/2010/02/10/html5-and-flash/
- 105 http://www.alistapart.com/articles/flashstandards/
- 106 http://news.zdnet.com/2100-3515_22-199508.html