Adobe Flex SDK

» see adobe.com/products/flex as it lived, on the wayback machine

~ the last words ~

adobe flex sat in a part of the industry i never worked in. in the late 2000s the flex jobs in turkey were bank dashboards and crm consoles, which was the same crowd that did sap netweaver and oracle forms. i was on the embedded vision side of the curriculum at the same time, c++ on a workstation, opencv on a webcam, nothing that touched a swf file. flex was a name on linkedin job listings i scrolled past.

jeremy allaire and the macromedia royale team shipped flex 1.0 on 20 june 2004 as a j2ee server product that compiled mxml into a flash swf at runtime. version 2 in june 2006 moved the compiler offline and made the runtime libraries open. by then macromedia was inside adobe and flex was the enterprise face of the flash platform, paired with flex builder as the eclipse ide on the developer side. the bet was that a designer could mock a ui in illustrator, hand the asset to a flex developer, and ship a desktop-grade application that ran in any browser with flash player installed.

that bet had a window of about five years. by '08 the flex ecosystem had real customers, sap netweaver bi 7.0 used a flex frontend, salesforce had a flex sales console, bloomberg shipped a flex terminal. the framework also picked up the rich-banking-dashboard market in europe and the bric countries because flash player install base was effectively universal and the alternative was an applet. on 18 november 2011 adobe announced flex was being donated to the apache software foundation, the same week steve jobs's open letter on flash had finally turned into a flash player mobile shutdown. apache took the source in early 2012 and apache flex 4.16 still shipped in 2017, the commercial flex story stopped in 2011.

~ the record ~

~ what it was supposed to be ~

the flex pitch was that html could not build a real desktop application in a browser. that was true in 2004. mxml gave you a button, a datagrid, a treeview and a chart out of the box, with css styling and a binding syntax that updated the ui when the model changed. you wrote the business logic in actionscript 3 and the runtime was flash player, which by then ran on ninety-eight percent of desktop browsers. the apps looked like windows forms inside a chrome tab. that was the entire selling point against a server-rendered jsp page.

the framework had a real component library, a unit-testing harness called fluint, and a profiler that worked. enterprise teams who used to ship swing applets switched to flex because the deployment story was simpler. there was no jvm to install, the browser already had flash. for a few years around 2008 the flex consulting market in london, frankfurt and istanbul paid better than the corresponding java market for the same kind of dashboard work.

~ how the donation happened ~

on 11 november 2011 adobe published a roadmap pdf that said flash player mobile would stop shipping. four days later a second post said flex was going to apache. the timing was not a coincidence, adobe was exiting flash on the consumer side and could not justify keeping a paid commercial framework alive on the enterprise side. the apache donation included the sdk, the compiler, the component library and the documentation. flex builder, the commercial eclipse ide, stayed at adobe and got renamed flash builder for one more release. the open-source migration shipped as apache flex 4.8 in july 2012.

~ the legacy ~

this part you had to be in the enterprise world for, and i was in the academic embedded one. apache flex still has occasional commits in 2026, the active project is apache royale, a transpiler that takes mxml and actionscript and emits javascript instead of swf. the existing flex applications still in production were mostly rewritten as react or angular spas across the second half of the 2010s. some sap dashboards reportedly held out into 2018 because the migration cost was higher than the support cost.

the cultural residue of flex is the entire enterprise rich-client pattern that came back as electron a decade later. flex got the desktop-in-the-browser idea right and got the runtime wrong. javascript caught up to actionscript 3 by '13 and the rest of the framework's design problems were already solved on the html side by then.

@}-->--

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

« previous  ·  random  ·  next »