Adobe Flash Catalyst

~ the obit ~

adobe flash catalyst was the kind of product designers reached for when they needed to ship a flex prototype to a developer in 2010. that was not me. honestly i was in the middle of an embedded vision thesis in those years, the closest i came to a flex application ui was a corporate dashboard somebody else built that i had to feed sensor data into. flash catalyst sat in a workflow between illustrator and a flex developer, and that workflow did not run through any project i actually worked on.

look, the product had a much longer prehistory than the public release. macromedia had been showing a tool called thermo at the max conferences since around 2007, the pitch was that a designer could take an illustrator or photoshop layer and turn the static asset into a clickable prototype with state transitions, without writing any actionscript. for some reason, the thermo prototype kept slipping inside macromedia and then inside adobe after the 2005 acquisition. flash catalyst finally shipped on april 30 2010 as part of creative suite 5, branded as a peer to flash builder rather than as a flash-pro extension.

from looking at the adobe forums and the cs5.5 release notes. anyway, the actual workflow was a bridge format called fxg, a flex-friendly subset of svg that the designer exported from illustrator and that flash catalyst loaded as the basis for the prototype. by '11 the cs5.5 update tried to tighten the back-and-forth between flash catalyst and flash builder, the file format friction never quite went away. then in april 2012 adobe shut the product down with no upgrade path into creative suite 6.

~ the rap sheet ~

~ the funny part ~

the timing was bad in a way that was almost visible from the start. flash catalyst shipped in april 2010, the same month steve jobs published the open letter on flash that explained why ios would never support it. honestly the writing on flash as a consumer-web technology had been on the wall since the iphone shipped in 2007 without flash support. by the time flash catalyst was in cs5 boxes on the shelf, the strategic question for the flash platform was about enterprise rich-internet-applications rather than youtube videos or banner ads.

adobe tried to keep flex alive as a sap-style enterprise rich-client platform after donating it to the apache foundation in late 2011 as apache flex. for some reason, flash catalyst's designer-to-flex workflow was tied closely to adobe's commercial flash builder rather than to the apache flex toolchain, the consumer-side reason to use flash catalyst evaporated when the consumer side of flash evaporated.

~ what it became ~

adobe pivoted to html5 tooling around the same window. edge animate (in our graves under adobe-edge-animate) was the html5 successor on the timeline-animation side, edge inspect was the device-preview side, edge code was the html-editor side that ran on the brackets stack. flash catalyst as a separate product never made the jump into the edge family. the designer-to-developer workflow it was built around moved into a different toolchain entirely with adobe xd much later in 2016, which itself was eventually killed for figma reasons.

in 2026 flash catalyst is a creative suite 5.5 dvd image you can find on internet archive if you want to run it under a creative cloud 2014 license. that path does work for archival reasons. honestly, the fxg files those prototypes produced are mostly unreadable by anything that ships today. the macromedia-era thermo bet on designer-to-developer asset handoff was right about the workflow and wrong about the runtime. flash was the wrong runtime by the time the product finally shipped.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »