Summary: Although multimedia has its role on the Web, current Flash technology tends to discourage usability for three reasons: it makes bad design more likely, it breaks with the Web's fundamental interaction style, and it consumes resources that would be better spent enhancing a site's core value.
About 99% of the time, the presence of Flash on a website constitutes a usability disease. Although there are rare occurrences of good Flash design (it even adds value on occasion), the use of Flash typically lowers usability. In most cases, we would be better off if these multimedia objects were removed.
Flash tends to degrade websites for three reasons: it encourages design abuse, it breaks with the Web's fundamental interaction principles, and it distracts attention from the site's core value.
Encourages Design AbuseSplash pages were an early sin of abusive Web design. Luckily, almost all professional websites have removed this usability barrier. However, we're now seeing the rise of Flash intros that have the same obnoxious effect: They delay users' ability to get what they came for. On the upside, most Flash intros feature a "skip intro" button. However, their very existence encourages design abuse in several ways.
First, Flash encourages gratuitous animation: Since we can make things move, why not make things move? Animation clearly has its place in online communication. However, as my 1995 guidelines discuss, that place is limited.
Second, one of the Web's most powerful features is that it lets users control their own destiny. Users go where they want, when they want. This quality is what makes the Web so usable, despite its many usability problems. Unfortunately, many Flash designers decrease the granularity of user control and revert to presentation styles that resemble television rather than interactive media. Websites that force users to sit through sequences with nothing to do will be boring and pacifying, regardless of how cool they look.
Third, many Flash designers introduce their own nonstandard GUI controls. How many scrollbar designs do we need? Actually, we probably do need a new scrollbar design for online content; the current scrollbar was designed for office automation content that users wrote themselves. However, the specification of a new GUI widget is a major human-factors exercise. The current Macintosh and Windows scrollbars emerged after the world's best interaction designers worked for years testing numerous design alternatives. A new scrollbar designed over the weekend is likely to get many details wrong. And, even if the new design was workable, it would still reduce a site's overall usability because users would have to figure out how it worked. They know how to operate the standard widget. When you use standards, users can focus on content and their reasons for visiting your site. Deviate, and you reduce their feeling of environmental mastery.
None of these usability problems are inherent in Flash. You can design usable multimedia objects that comply with the guidelines and are easy to use. The problem is simply that current Flash design tends to encourage abuse.
Breaks Web FundamentalsThe second set of issues relates to the very notion of using a plug-in rather than standard Web technology. In the future, multimedia features may well be better integrated with browsers and thus these problems will be solved. For now, though, the fact that Flash is not standard HTML creates a host of nasty usability issues:
Perhaps the worst problem with Flash is that its use consumes resources that would be better spent enhancing the website's core value by:
If Flash was cheap to produce and if all content creators could make a Flash object as easily as they write a standard Web page, then perhaps many of these problems would be alleviated. For now, they remain serious issues. I thus recommend that Web designers interested in enhancing usability and their site's overall business presence use Flash sparingly.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3