Every year, we make technology predictions about the various content technology marketplaces that we cover. And rather uniquely, we go back and see how we fared. So here's how we fared with our 2013 predictions:
Along with asset ingest and processing, metadata management is one of the staples of any DAM system. Or so it should be. But as reality shows, I am still yet to encounter a DAM user who is content with how their system handles metadata.
To be sure, deliverability is a multi-dimensional challenge: you have to pay attention to myriad details ranging from
In my conversations with digital workplace and marketing technology leaders, they tend to laud the long decline and potential demise of BlackBerry and Windows Mobile. Not because they dislike those platforms (though many do), but because mobile leaders believe that shaping effective mobile experiences for customers and employees gets much simpler with only two big client environments -- iOS and Android -- in the picture
In our WCM selection advisory services, user security and entitlements continue to come up as tricky issues. These are certainly not new challenges, but vendors address them in different ways, and certainly customers vary in their requirements here. So to provide a little education, below I've excerpted bits of the front matter from
Salesforce.com has a gap in their marketing cloud in the key area of Marketing Automation (MA). In general this is not a bad thing, since they integrate with several other MA vendors instead
When Microsoft began releasing betas of Internet Explorer 9 in 2010, Redmond's huge global user community quickly started uncovering various strengths and weaknesses of the new version. One demerit quickly emerged that still hasn't completely gone away: IE9 doesn't play well with certain versions of the popular rich text editor ("RTE") TinyMCE as well as its main competitor, FCK/CK
The whole affaire, as well as a recent request I received from a Digital Asset Management vendor, reminded me that the world of technology analysis is no less shifty -- it's just that the attempted manipulation of the system for personal and business gain is of a different nature
I recently spoke at the HartmanEvent in Utrecht, Netherlands, on "Why You Don’t Need CXM Platforms" -- a topic near to my technology heart that I’ve discussed on this blog and in other outlets before.
If there's one legacy I'd like from the games of 2012, it would be a renewed enthusiasm for building accessible websites and not -- as in the case of Ocado -- aiming so low as to hit only the most-basic level of compliance
I might be missing something, but my question remains: what specifically are WCXM vendors trying to prove by focusing on Responsive Design? That they won't actively prevent you from using CSS3?
In the past -- in my typical skeptical manner -- I suggested that relying on the mere existence of an API was a bit risky when it comes to integrations. What has happened in recent times with Twitter puts a different spin on this topic, namely: what happens when that API just goes away?
Last week, Facebook announced a new application for iPhone and iPad devices that runs on Apple's iOS mobile operating system. This application is a native app -- meaning it's written using Apple's proprietary technologies and you must download it from Apple's App Store.
This represents an about-face
The esteemed Financial Times is ready to pull the plug on its iOS native apps and instead replace them with an HTML5-based app.
Reportedly, the so called "Apple Tax" -- whereby developers pay 30% of revenues to Apple -- along with lack of access to customer data, are the main reasons prompting FT.com to follow others