We built a Flex application for an insurance company's CSRs. It was - as Troy mentioned for one of his projects - because the executive stakeholder heard of this Flex-thing and wanted to whiz-bang. I had done Flash in the past, so I was tapped to learn Flex and go from there. When it dealt with out-of-the-box needs, it was great - easy, I learned on the fly, I produced the basic application in a little over a week...and it became easier as I went along. When I started hitting walls, we had to backtrack and re-engineer because our IAs and their system requirements didn't mesh - and well,I'll say it - they had no idea of the capacities or limitations of the technology. When we were done (and it took our engineers extra time to integrate the backend, but they were learning as well), I was able to complete something in a week and a half (with 3 days help from a seasoned contractor) that would have taken me about 3 weeks in HTML/Ajax - a nice slice off the time, even if not revolutionary. However, for such an easy-to-learn technology and usable platform, it gave me a daily headache. Since then, I've advised against Flex for every project which has been brought up - not because I don't think it has uses, it's just not the right tool for the problems presented...and people are still learning what it is and isn't.
Scott ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
