It is with great pleasure that we introduce to you the next release of the Flex SDK, code-named Hero. The Hero release has three main themes:

  • Multi-Screen Development: Allow developers to build applications that target the web, desktop or mobile devices using a single unified framework.
  • Spark Maturation: Polish and grow the Spark architecture by adding new Spark components and capabilities.
  • Large-Application Development: Support developers building large applications by improving fundamental Flex infrastructure pieces.

What’s even more exciting is that these three themes are being satisfied by taking advantage of new features in the next generation Flash Player and AIR runtimes. As those runtimes become publicly available, you will be able to download Hero builds and exercise in-development Hero features in order to learn and provide feedback.

Let’s dive into more detail for each of these themes.

Multi-Screen Development

We are currently building new mobile development capabilities into the Flex framework. The Hero release of Flex will enable developers to continue to create application experiences that translate well across platforms, in addition to making it easy to build applications that work well on a wide variety of mobile devices. Hero will augment a number of existing Flex components with mobile- and touch-optimized skins and functionality and will also add new components that support mobile-specific UI patterns. Developers already familiar with core Flex concepts like data binding, MXML and dynamic layout will be able to quickly leverage that knowledge into building applications that can target numerous mobile devices.

Previously, we had investigated splitting off mobile development into a separate, new branch of the Flex framework, code-named Slider. However, the rapid increases in performance on smartphone-class devices over the past year, combined with the highly optimized performance of Adobe runtimes on these devices, now make it feasible to support mobile use cases directly with the core Flex framework. This unification of both mobile- and desktop-targeted features into a single framework is one of the cornerstones of the Hero release.

You can learn much more about the mobile features targeted for the Hero release by reading the Flex and Mobile Whitepaper and the Flex and Mobile FAQ, as well as perusing Hero Mobile feature specifications on the new Hero open source site.

Spark Maturation

With the Flex 4 release, we introduced a new component and skinning architecture called Spark which allows for designers and developers to separate component logic from behavior and declaratively customize the visuals of a component. Spark has proven to be a key addition to the Flex framework, and the Hero release focuses on building more Spark-based components as well as providing new Spark capabilities to existing Flex features. Some of the new Spark components being offered in the Hero release include Spark Form, Spark Image and Spark DataGrid controls. These new Spark components not only provide parity with the previous MX versions, but also expose capabilities that allow for more modern component designs.

Large-Application Development

As people use Flex to build much more complex and mature applications, core pieces of the Flex framework must be retrofitted in order to support these efforts. The Hero release aims to improve the compilation experience (with regards to full and incremental compilation times as well as memory consumed during compilation) for large applications that make heavy use of modules or themes. Additionally, the support for linking runtime shared libraries has been enhanced to allow for smaller download size and faster startup time. You can read more information about the changes to RSL linkage by reading the Hero feature specification here.

Changes to Build Availability

More so then ever before, the Flex SDK is tied directly to the evolution of Flash Player and AIR. The Hero release is being built atop the latest, in-development (and as of yet un-released) Flash Player and AIR runtimes. Because of this tight coupling, we are unable to provide nightly builds that showcase in-development Flash Player and AIR features. Once the current in-development Flash Player and AIR runtimes are showcased in a public release, Hero nightly builds will resume. In the interim, we will release semi-regular builds that showcase Hero features not dependent on features under development in the latest Flash Player and AIR runtimes. We will be posting the first of such builds over the next coming days. These special builds will feature several of the items mentioned in the Spark Maturation and Large-Application Development themes above. Builds showcasing Hero mobile capabilities will follow in later months. Watch the Hero open source site for more information.

More Information

This is just the start of many documents outlining new features in the Hero release. Keep an eye on the Hero open source site for the sharing of whitepapers, special Hero builds, feature specifications and design documents. Additionally, we will soon be announcing our first Hero Open Iteration Meeting, where work completed in past iterations is reviewed and upcoming feature work is previewed. Also, you can find out more about AIR for Android and participate in the pre-release program by going here. We hope you are just as excited as we are with all of the new applications and workflows Hero will enable you to build!

Flex SDK Product Team

10 Responses to Introducing….Hero!

  1. Arun Sarma says:

    “Hero” should be the real hero!

  2. Borek says:

    Mobile store of Hero looks fantastic and the large-scale apps improvements will also be very welcome but it would be great if the Spark updates/components could be released sooner than in 2 years time (as is the standard Flex SDK release cycle if we can judge from the past). Something like the proposed Flex Control Toolkit would be fantastic (

  3. Tom Gruszowski says:

    Exciting news!So is Hero Flex 4.5 or is it the product following 4.5 release?Will Hero let us use 100% spark or will there still be a MX parity discrepancy for things like charting and AdvancedDataGrid? Will ADG even be necessary with the new DG?

  4. Marcus Stade says:

    Wow, that was fast. Gumbo has been out for what, five minutes? =)I like the direction in which you’re going, with more and earlier information to developers. This’ll surely be helpful when convincing clients that yes, it makes sense to upgrade since we developers will be much more knowledgable.However, this little tidbit was the most interesting bit I’d say:”The Hero release is built atop the latest (and as of yet, unreleased) Flash Player and AIR runtimes. Because of this tight coupling, we are unable to provide nightly builds that showcase in-development Flash Player and AIR features.”What does this mean? I realize you can’t divulge details, but reading between the lines it sounds as though there’s some interesting new developments in the Flash Player that might actually involve language enhancements. Don’t get me wrong, the last few players have been monumental steps in the right direction, but AS3 – released no less than four (!) years ago, almost to the day – has seen ridiculously few improvements in areas where it could really use some (generics, anyone?)This is all wonderful news, especially hearing that you will focus on making Spark mature (it’s a great framework!), but I’d absolutely love it if your “one more thing” would be language enhancements! ;o)PS. Your captcha is brutal.

  5. Mayur Rami says:

    Adobe Flex ” Hero “It really makes us happy.Adobe Rocks Again…

  6. emurmur says:

    I do like the idea of targeting multiple screens with a single SDK. However, integrating this so closely with an as-yet-unreleased player means that we have to wait longer for a mobile Flex solution. I would prefer a mobile framework that targets 10.1 sooner than later. Having a mobile option ASAP is much more important than having a single SDK for multiple screens. We need a solution as soon as 10.1 appears on our phones (soon, hopefully).

  7. judah says:

    …did u ever know that you’re my heeeeerooooo?

  8. @Lisa – The version of OSMF shipped in 4.1 is the same version that shipped in 4.0. We are looking to integrate OSMF 1.0 into the next release of Flex (code-named Hero).

  9. Lisa says:

    What version of OSMF ships with 4.1? Are the two lines now integrated?