My Flex 2010 Wish List

Monday, January 04, 2010
I can't believe 2009 is already over. But now that it is, its time to look forward to 2010. Adobe is planning on new releases of the Flex SDK, Flash Builder, and the 10.1 Flash Player this year so we all have reason to be excited. (Oh and don't forget SourceMate too). Its probably too late to influence these new 2010 releases, but I'm still going to throw out my Flex wish list for the future.

Fortunately my wish list isn't really very long. In fact, I only have two real items:

Full HTML browser within Flex

Today you can't really integrate HTML content into a Flex application. There are a few tricky solutions (mostly provided by floating an iframe on top of the Flash player). Unfortunately these have all kinds of problems. First, we have to change the wmode of the player for these to even work - and that immediately prevents screen readers from working. So enterprise applications where 508 compliance is required can't even contemplate these solutions. And even when we can use them, we're still stuck with other limitations as the actual HTML content is floating above our app and not really inside it.

To some people this might not seem like a very important feature request, but I've found quite the opposite. Every customer or potential customer I speak with runs into this. Portals/portlets are still all the rage (right or wrongly). Customers want a portal application where they can embed both HTML/JS portlets and Flash portlets. These customers have to choose HTML as their main platform (i.e. the container) rather than Flex. Other times, customers have an existing Java-based web app that they'd like to transition over to Flex. The keyword is transition. They can't just throw away their existing app and start over. They need to replace it bit by bit. But the architectures of Flex and the Web 1.0 world of these legacy Java web apps don't mix well. Ideally, they could rewrite the main frame of the application in Flex and pull in pages (say in a tab folder or something similar) of the old web app. Right now, thats not really feasible.

This is the #1 reason (in my experience) why organizations don't choose Flex.

Flex Compiler Performance Improvements

The Flex compiler is slooooow. Its been improved noticeably with Flex4. But its still too slow. On large projects its horrendously slow. This is one aspect where Flex and Flash Builder do not compare favorably with HTML/JS (obviously no compiling there) but also with Java or any other platform I've had recent experience with. I still believe developing with Flex, due to the productivity of the architecture, Actionscript language, and Flash Builder IDE is levels of magnitude better than AJAX. Yet, I can't stand the constant interruptions while I wait for the Flex compiler to finish. Fast is a feature!

To Adobe's credit, they do appear to be working on it. I just hope the work done in the Flex 4 cycle is the beginning and not the end of the improvements.

These two changes arise from the experience of Java developers moving to Flex - both my own experience, and what I've gleaned from talking to customers and their developers about moving to Flex. If Adobe resolves these, I think we'd see more Java developers happily using Flex in the future.


  • I totally agree with need for a full browser support within flex. Not having the browser makes it incredibly hard to perform a transition of a 1.0 application to a flex based solution.

  • James Ward

    Hi Chris. Thanks for posting this. You should make sure you go vote for this feature request:

    Also, you don't have to use wmode transparent to do the iframe. But there are so many other issues with iframes that solving that one issue doesn't make the iframe approach feasible in most cases.

    Another approach is the flex-htmlfilter project:

    But it's pretty limited in the HTML it supports and will likely never be a full browser implementation.

    Anyway, Happy New Year!


  • Chris

    Thanks James. I'll add my vote (if I haven't already). I know this is a very difficult problem to solve (full HTML browser engine) but its (IMO) critical.


  • Eric Wendelin

    I've done very little with Flex but I've already run into problems with a lack of a full HTML browser engine. +1 there.

  • Tejas application has really been it's large project :(

  • Softmod Wii

    So enterprise applications where 508 compliance is required can't even contemplate these solutions. And even when we can use them, we're still stuck with other limitations as the actual HTML content is floating above our app and not really inside it.

  • 646-205

    I found your website perfect for my needs. It contains wonderful and helpful posts. I have read most of them and got a lot from them.

  • Jelly sandals

    The blog was absolutely fantastic as there are lots of great information and inspiration.

  • motorcycle clothing

    I would like to thank you for the efforts you have made in composing this article. thanks for sharing the great information.

  • Testking 642-813

    These kind of post are always inspiring and I prefer to read quality content so I happy to find many good point here in the post, writing is simply great.

  • rose perfume

    That is some inspirational stuff. Thanks for all the enthusiasm to offer such helpful information here.

    I am really interested in this program. Nice, and thanks for sharing this info with us. Good Luck.

  • Viagra without a prescription

    Any plans to add a vertical window shade component? Or extend the present shade to allow it to be used vertically (eg unroll from the left or right)

  • Post a Comment