When Flash was the future

There was a period where the most interesting interaction design on the web happened in Flash.

Not the banner ads. Not the annoying splash screens with a “skip intro” button. I mean the studios — Hi-Res!, 2Advanced, Yugo Nakamura’s work at Yugop — who were doing things with motion and interaction that felt genuinely impossible anywhere else. I spent hours reverse-engineering them, trying to understand how something that fluid could be built in a browser.

I never became a Flash developer. But I watched Flash closely, and it shaped how I think about movement and time on the web.

What Flash got right

Flash had a timeline. You thought about your interface in terms of states, transitions, and duration. You didn’t just make something appear — you made it arrive. The physics of how UI elements moved communicated something about what they were doing.

CSS didn’t have transitions until 2009. JavaScript animation was janky and inconsistent. Flash’s tools for thinking about motion were better, and the work reflected that.

What Flash got wrong

Flash was a black box to the browser. Screen readers couldn’t see it. Search engines couldn’t index it. It was a plugin that could be — and eventually was — turned off. All that beautiful interaction design was built on a foundation that the open web never agreed to.

The web standards people had this argument with the Flash community for years. In retrospect, they were right about the architecture. But the Flash people were right about the ambition.

What we inherited

The motion design vocabulary Flash pioneered eventually became the expectation for what web interfaces should feel like. When CSS transitions and transforms finally arrived, we spent years trying to recreate what Flash had done naturally. Web Animation API, CSS animations, JavaScript physics libraries — all of it is, in some sense, an attempt to get back something that was lost.

I still think the best interaction design on the web acknowledges that UI has time, not just space.