Get the real story via our bi-monthly newsletter

Search

    4
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > In DAM, Flashy does not always mean Flex

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends

Enterprise Social Software & Collaboration Trends


Report Excerpt

The Digital & Media Asset Management Report looks at... The MAM pairing of IBM's FileNet & Ancept Media Server

"FileNet was (and is) rightly renowned for its document-imaging, distribution, and process automation prowess. It has a well-proven ability to scale and its object-oriented content model is essentially agnostic as to content type, making it an appealing platform for DAM. Somehow, FileNet Corporation never saw fit to try to exploit the DAM market. IBM has other plans, it seems."

(p. 179)

More about The Digital & Media Asset Management Report

Our customers say

"CMS Watch put their trademark stamp of insight, depth of understanding, candor and overall industry smarts in The Digital & Media Asset Management Report. For anyone working to develop an understanding of what digital asset management is, or what lessons can be distilled from dozens of first- and second- generation implementations, or read a perceptive, engaging recap of the vendor landscape, this is an outstanding resource. With a level of readability that makes the content accessible, at-your-fingertips, and ready-to-use, this report is a long-awaited contribution to the field of digital asset management.
- - David Lipsey,
Managing Director, Global Practice, Media & Entertainment -- FTI Consulting

NEW at CMS Watch

The Search and Information Access ReportThe Search & Information Access Report: This newly updated 341-page Search and Information Access Report critically evaluates 23 Search and Information Access offerings from around the globe... Read more

The Enterprise Collaboration & Community Software ReportThe Enterprise Collaboration & Community Software Report : This newly updated research critically evaluates 27 Enterprise Collaboration and Community Software products head-to-head... Read more

The Enterprise Content Management ReportThe Enterprise Content Management Report : This newly updated research critically evaluates 32 Enterprise Content Management products head-to-head... Read more

 
 

TrendWatch Blog

In DAM, Flashy does not always mean Flex

11-Jun-2009   --  

I mentioned in an earlier post (about the recent Henry Stewart DAM Symposium) that one of the big trends right now in the DAM world is a shift toward client apps built on Adobe Flex technology. Sometimes it's hard to tell the Flex from the non-Flex players, however, because the grey-on-grey look and feel can also be achieved with ordinary HTML and CSS, and some vendors have actually used those technologies to achieve a distinctly Flex-like appearance for their new UIs.

A good case in point is MediaBeacon, whose R3volution 3.0 product has such a convincingly Adobe-like facade that I mistook it for Flex technology the first time I saw it. But it's actually straight HTML, CSS, and JavaScript.

MediaBeacon made a conscious decision to avoid Flex, not so much for technology reasons per se, but for larger concerns around Web standards. The company's CTO, Jason Bright, explains it this way: "Flex, like ActiveX, Silverlight, and Java Applets before them are, in a sense, replacements to the browser. Each replaces the web browser in a proprietary way. While I love Flex as a technology, I do not think it is a good strategic decision to throw out the traditional browser for a new client-server model no matter how attractive."

Part of the issue, says Bright, is the fact that Flash requires a plug-in -- it's not a browser-native runtime (any more than Java is). He adds: "Things like AJAX and HTML, driven by powerful libraries like Google Web Toolkit, allow apps to have just as much power as Flex, without replacing the web browser's native rendering capabilities." Plug-in technologies, Bright seems to be suggesting, do not steer the direction of web development. And historically, that's certainly been true.

But by the same token, web-apps that run inside the firewall (WCM and DAM apps in particular) are not necessarily subject to the same constraints as public-facing web-apps. An enterprise can choose to standardize on (or mandate use of) Java -- and Java applet technology -- or not. The same is true for Flex. Inside the enterprise, the rules are different.

Just bear in mind that the vendors who are switching to Flex are taking a gamble, and if you go that way, you're taking the same gamble. Plain old AJAX and HTML, right now, are the "tried-and-true" technologies of the browser-client world, and likely will be for a while. Bear that in mind as you go shopping for "new, improved" WCM and DAM systems.

- Submitted by: Kas Thomas, Analyst - Twitter: kasthomas

All DAM Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us




Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

3470 Olney-Laytonsville Road Suite 131

Olney, MD USA 20832

1 800 325 6190

1 617 340 6464

UK: +44 2033181911

Fax: +1 617 340 3541