Is Apache Flex Still Usable After Flash Player Browser Support Ends?

Updated

Apache Flex remains usable, but not for browser-based Flash content. The project's own site states that Adobe and all major browser vendors ended support for the Adobe Flash Player runtime at the end of 2020, and directs anyone who needs to output content to the browser toward the sister project Apache Royale, which lets you keep ActionScript while producing native JavaScript and HTML. Flex output to mobile and desktop platforms through the Adobe AIR runtime, provided by Harman, is still supported.

What changed, and what still works

The key distinction is the target platform, not the framework itself:

Target Status per the Apache Flex site Practical path
Browser (Flash Player) Support ended at the end of 2020 across Chrome, Firefox, Edge and others Move browser output to Apache Royale
Desktop apps via Adobe AIR Still supported (AIR provided by Harman) Continue building or maintaining AIR desktop apps
Mobile apps via Adobe AIR Still supported (AIR provided by Harman) Continue targeting mobile through AIR

The site also notes that Flex applications have historically targeted "all browsers by leveraging the Adobe Flash Player and JavaScript," and that mobile targets included iOS devices, Android phones and tablets, and BlackBerry Playbook. The browser leg of that list is the part affected by the Flash Player shutdown.

Why the framework itself is not the problem

Apache Flex is an open-source framework released under the Apache License 2.0, backed by the Apache community for updates and support. Nothing about the license or the project's governance changed with the end of Flash Player. What changed is the runtime that browser-delivered Flex content depended on. That is why the site's guidance is about redirecting browser output to Royale rather than about Flex being discontinued.

Flex uses MXML for layout and ActionScript 3 (an ECMAScript-based language) for coding, and the site points to Eclipse-based IDEs such as Adobe Flash Builder and FDT, or the command-line compiler, as tooling. Those development workflows are unaffected by the browser runtime question.

Deciding what to do with an existing Flex application

The decision hinges on where your application runs today:

  • Browser-delivered Flash content: Plan a migration. The site's recommended route is Apache Royale, which preserves ActionScript skills while outputting native JavaScript and HTML. Treat this as a rewrite of the delivery layer, not a recompile.
  • Desktop application on Adobe AIR: You can keep it running and maintained, since AIR support continues through Harman. Confirm your AIR runtime distribution and update path with Harman as part of normal maintenance.
  • Mobile application on Adobe AIR: Same as desktop — supported, with the same caveat about sourcing the AIR runtime from Harman.
  • Mixed codebase: Separate the shared business logic from the presentation layer. The ActionScript logic is the part most likely to carry over to Royale, while Flash-dependent UI and browser integration will need rework.

Practical next steps

  1. Inventory where each application actually executes — browser plugin, AIR desktop, or AIR mobile. The site's own framing makes this the deciding factor.
  2. For browser targets, review Apache Royale's documentation and getting-started material before committing to a migration plan; the site positions it explicitly as the path for continuing to use ActionScript with JavaScript/HTML output.
  3. For AIR targets, verify your current runtime version and support arrangements with Harman, since AIR is provided by them rather than by Adobe.
  4. Check the Flex project's download and documentation pages for current SDK, FlexJS (marked beta on the site), and FlexUnit materials if you are maintaining or starting development.

The short answer for planning purposes: Flex is alive as a framework, AIR-delivered desktop and mobile apps remain supported, and browser output needs to move to Apache Royale.