Adobe Experience Manager Review
Anonymous | TrustRadius Reviewer
November 18, 2016

Adobe Experience Manager Review

Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Adobe Experience Manager

My company implements Adobe Experience Manager solutions on behalf of others.
  • Give content editors an easy and intuitive interface to manage content. For example the WCM allows users to create and edit pages. The page editor allows the users to navigate the DAM and drag/drop images onto the page. Once done editing, they can submit the page into a workflow for manager review.
  • Give managers the tools to establish an editorial workflow to better control what is published. Managers can create custom workflows, often with out of the box components (there is a workflow editor) to allow them to control the review and publishing of content.
  • Based on Open Source so it is easier for developers to work with. There are at least 2 major OSS libraries out there, ACS Commons and WCM.IO.
  • Out of the box integrations with many other systems, especially the Adobe Marketing Cloud.
  • It is hard to find people with the skill to develop solutions on AEM.
  • The TouchUI pales in comparison to the features found in the Classic UI. Developers have a hard time implementing solutions in the new Touch UI because the framework is lacking, where as in the Classic UI the framework is more robust. For example there are some out of the box classic UI widgets that allow developers to create key/value pair lists in dialogs. In touch ui that does not exists and developers are forced to implement custom solutions.
  • It is based on open source, so a lot of the code base is out there (except the proprietary AEM stuff, i.e. WCM). This means that between versions of AEM, there are major changes (they are good at backward compatibility however). This could be a good thing, but may be a bad thing if your company is more sensitive to big changes that come hard and fast. There are people out there developing on AEM 6.2, as if it were still AEM 5.6. They don't even know how to take advantage of the new features.
It really comes down to how much money you are willing to spend (Adobe is more) and the skill set of your developers (Sitecore is .NET vs. Adobe is Java).
It is well suited to put out traditional and informational intra/extranets where content editors create articles/posts; could even allow external users to contribute content, deliver your site to many channels. For example, aside from the traditional desktop site, there are AEM Publications and Mobile Apps.

It's not meant to be used as a CRM, it is supposed to integrate with one. It's not meant to be used as some management system. For example in previous experience, a customer was using it to manage requests (i.e. a JIRA type of thing).

Adobe Experience Manager Feature Ratings

WYSIWYG editor
10
Code quality / cleanliness
9
Admin section
9
Page templates
10
Library of website themes
Not Rated
Mobile optimization / responsive design
9
Publishing workflow
10
Form generator
Not Rated
Content taxonomy
10
SEO support
10
Bulk management
10
Availability / breadth of extensions
8
Community / comment management
8
API
10
Internationalization / multi-language
10
Role-based user permissions
9