The first time I saw Flash, I was a freelancer writer getting a demo from its creators on my dining room table. I was immediately impressed. But it wasn’t yet a Web animation/video/interactivity plug-in from Adobe. The year was 1994, and the software that knocked my socks off was a Windows drawing app called FutureSplash SmartSketch. The Web, animation, video, interactivity, and ownership by large companies (Macromedia, and then Adobe) all came later.
SmartSketch was cool because it was simple, fast, and hassle-free–and as much as as the software changed once it morphed into a Web tool, it maintained those virtues for a long time. Back in the dial-up era, it was a joy; years later, it was the first technology that made Web video make sense.
As the Apple-Adobe wars have raged, I’ve been thinking about Flash’s origins and current condition. Flash is still important and useful, but it long ago stopped being the almost endearing technology it once was. I think that helps explain why there hasn’t been more of a groundswell of support for Adobe–people who care about Flash at all have mixed feelings about it. (Back in October, almost half of Technologizer readers who participated in my wholly unscientific poll thought Flash on smartphones sounded “downright irritating”–and only eight percent were excited by the prospect.)
Here’s what happened over the past few years:
Flash got unreliable. On some of my computers, in some some browsers, it works fine. But while I was writing this post in Google Chrome, I got a message saying Flash had crashed–and the whole browser was rendered unusable. (Hey, I thought Chrome was designed to make that impossible…)
Flash got cumbersome. I went through a bout of it constantly telling me I needed to allocate more memory–which was a problem in itself. Even worse: The interface it provided for doing so was hopelessly confusing.
Flash got abused. Starting early on. Especially by misguided Web designers who built pointless intro screens that did absolutely nothing for consumers except make it harder to get anything done on the site in question. (If I were Adobe, I’d bribe sites if necessary to dump Flash intros–they’ve been enormously damaging to the software’s reputation)
Flash didn’t evolve fast enough in the right direction. The last gigantic tangible improvement–and the one that kept Flash as important as it is–was video support. But for eons, Macromedia and Adobe have failed to seize the opportunity to make Flash as important in the mobile world as it has been on the desktop. (Here’s a press release from early 2000–!–about Flash on phones; ten years later, you still can’t get real Flash on a smartphone.)
Some of the current Flash-bashing is a little overwrought–and with HTML5 and other truly open standards starting to encroach on Flash’s territory, I think we’d be at the beginning of the end of Flash in its historic form no matter what.
But I can’t help but think there’s some alternate universe in which Adobe made different decisions about Flash over the past few years and Apple pretty much had no choice but to let it onto the iPhone. Wouldn’t it all be very different if Flash was generally regarded as a lovable good citizen rather than a necessary evil?
This story, "Flash: What Happened?" was originally published by Technologizer.