I have been invited by my colleagues to visit the Flex Customer Meeting, and I am getting to discuss some unofficial topics with the Flex SDK team. Deepa Subramaniam the Product Manager for Flex, Andrew Shorten Platform Evangelist for Adobe Air, Steven Strongrundan Adobe Flex SDK Developer, as well as many other Flex SDK members were present. Some of the attendees from the consumer side of the meeting were Wells Fargo, Morgan Stanley, Sharp Healthcare, VMWare and Fidelity Investments. This was a very small meeting and thanks so much for the invite.
Seems as though concerns around if Adobe Flex within enterprises is considered a dying platform. There apparently is a strong contention that HTML 5 is applying pressure to CIO’s of top enterprise flex users to consider stopping with Flex and using things like Sencha Touch or JQuery to implement rich interfaces.
Testing is also a concern not only Unit Testing but also Functional testing of visual components. The claim from Deepa is that the unit testing framework created by adobe for validating the framework itself will be open sourced in the future to help show off ways to improve our unit testing and functional automation of flex applications. I can definitely say this is a pain point for me and I have yet to see a good implementation of this aside from testing Presentation Models and Remote services.
508 compliance is a interest to enterprise customers and in the Road Map talk it was definitely mentioned that it would be improved in the future. IAccesible2 is the interface that the Flash Player team is focusing on improving this featureset
I asked the question regarding if the Flash Player code could be open sourced given that it is consistently in contention against HTML 5 as an unstable platform. Given it’s blackbox nature maybe providing the source to the community to allow us to improve problems where they exist may improve the platform and rejuvenate its use in Enterprise applications. In response to that it is re-evaluated regularly every year, however there is no plan to open source the platform in the near future.
There was a need expressed to display HTML content and PDF content inside of flex applications due to the current lack of support for both of these. Maybe we will see that in the near future – no promises were made.
Security of SWF distribution and Air app distribution was expressed by a developer who feels the current state of Obfuscation tools and security is a bit lacking. He requested a solution for the security to be added to the FlashPlayer
Flex/Spark questions about some of the missing feature parity and the methods of migrating to the new platform were asked. As Deepa said in her discussion yesterday the feature gap is going to closed at worst in the next two minor releases. Charting components and Grid components are being released soon. Also Buttons with Icons are now in Here 4.5
Flex 3.6 has some bug fixes that will be released soon, but it is taking some time to finalize that release. There is no plan for many more builds after the 3.6 fix that comes off. Encouraging people to build off the 4.0 branch is the right thing to do according to Deepa. She is also claiming that there is no near term goal to deprecate the old MX components (hopefully obvious to everyone) but as the feature gap is closed it may come in the future.
A Morgan Stanley employee commented on the need for Concurrency to support real time updates on multi-screen applications which is a real need in Financial application development. It seems as though it is in agreement with the marketing and product management team. He also requested that the Grid be optimized for performance and to have a base performant data grid that has minimal features and then extensions to enable other features.
Someone from VMWare was wondering what happens when all of these enterprise applications migrate to Flex 4 / Spark components from their MX components and Flex 3 architectures. There seems to be a strong commitment from the Product Management at Adobe and Marketing to say that Flex 4 components are the direction to go and that it will be a long term focus for some time to come.
Another Morgan Stanley employee requested that the Jira found / fixed bug annotations be fixed to not say Moxie/Gumbo etc. Deepa said she is going to fix it next week.
I asked if the compiler direction with Falcon is going to close the API for things like IntelliJ and Flex Mojos for Maven. Deepa responded to say Marvin Froeder is working alongside the compiler team to add extensions and stay involved and they are working to tread the fine line carefully between being open and closed on their new compiler API.
Quite a lot of concern was voiced for the quality of training provided by Adobe for new developers. Also the lack of very complex examples are a huge problem with the state of the situation with regard to Flex Performance. There need to be more fundamental articles written to help explain how to use patterns properly in Flex. There were also voices requesting a better profile to help improve performance, specifically something that will make the profiler better will be the ability to export the data captured during a profiling session.