We’re starting to see more vendors coming out with Flex-based user interfaces, sometimes extending them as full-blown desktop applications using the AIR runtime. For example, Documentum’s D6 Web Publisher comes with a standalone Flex interface for certain tasks.
- Image via Wikipedia
We’re starting to see more vendors coming out with Flex-based user interfaces, sometimes extending them as full-blown desktop applications using the AIRruntime. For example, Documentum’s D6 Web Publisher comes with a standalone Flex interface for certain tasks.
To me, turning to Flex for a content management interface is a cop-out. It creates nice demoware for the vendor, but long-term problems for you. I can see why Flex is alluring for vendors: maintaining consistent, cross-browser compatibility (especially with AJAX) is hard and expensive. But why does that mean that you the customer must give up the simplicity and supportability of a native browser-based interface?
Flex is essentially another semi-thick client akin to Java applets (or ActiveX controls). Let’s review why the business world didn’t like applets for application user interfaces when they were pervasive within enterprise web applications earlier this decade.
Continues @http://www.cmswatch.com
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=8f9b9e2f-c2b6-4927-9a25-6fa1b5a6fded "The case against Flex-based application UIs 2")