I have been asked on occasion by clients, friends, and family if I would be willing to design a website that uses Adobe Flash. The short answer is no, the long answer is a tad more involved. Let’s break it down into a list, since I like lists.
Flash is standards free.
Flash is essentially exempt from any sort of standards oversight. It is an all-inclusive program that does little to encourage the development of a more open-standards web. Microsoft Silverlight suffers from this same problem.
Flash has a development entry fee.
For a person to develop a website using HTML, CSS, and Javascript (with images), all they need is a computer and a spark to learn the languages. This requires no capital, and there are many great programs and IDEs out there to make the job easier.
Flash, on the other hand, requires the purchase of Adobe’s Flash development software, which carries a hefty price tag. To a large development firm, this is a moot point. On the other hand, an at-home designer may struggle to justify the cost.
Adobe is slow to patch exploits & auto updates are non-intuitive.
Flash is known to be the target of many exploits, and Adobe is notoriously slow to address them. One of the more notorious in recent memory was the hacking of RSA Security, which was accomplished by taking advantage of an Adobe Flash zero-day exploit. Couple this paradigm with an unintuitive update notification system and you are begging for trouble.
Adobe desperately needs to accelerate their patch system, as well as implement a background-download auto update system to ensure their users are secure.
Flash is a resource burden.
Aside from requiring a ridiculously high 2.33ghz/1.8Ghz Dual Core processor, Flash is well known for sucking up resources and being a CPU hog in general. It is also crash-prone, which prompted Mozilla to put Flash content in a separate container process for their >3.6.4 versions of Firefox. This is so a crash in Flash wouldn’t take down the entire browsing session.
Flash prevents search engine indexing.
By and large, coding content in Flash excludes it from being indexed by search engine, because the text is not clearly formatting on the page and in the code. This often makes a designer resort to using a sitemap or some sort of non-compliant hack to make sure any content held in the Flash application is indexed by search engines.
It’s not all bad.
In general, I’m not saying that Flash is completely useless. Flash does a fine job of playing back video (the h.264 monopoly issue aside), as well as being a great setup for casual gaming. But, for the near future, I do not see my position changing much in regards to web design using Flash.
There are three major things I believe Adobe can do that will make Flash much easier to digest by HTML purists and open-web developers:
- Reduce the cost of the Flash Development kit, or release a free alternative.
- Create a background auto update system and accelerate the patching of zero-day and major exploits.
- Optimize performance by including more hardware acceleration and possibly speeding up the landing of multithreading support.
Once installed and started, WAMPServer runs in the Windows Tray, allowing quick access to configuration options.



