Item: Adobe Experience Manager
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

Like as part of marketing team, we are responsible for, you know maintaining and hosting the website for our company. Like and also we made a lot of other applications. So these earlier we were using another CMS solution, so last three years back we moved to AEM solution. Like considering like this product have lot of benefits and compared to the previous one, which you're using, among those that I would like to point out you like especially in the experience manager we can integrate easily with the other solutions like Target and, you know, easy to track that. And and we do, you know as a developer day to day, I face the problems. I think, most of them are rid of the experience Managership, right? And especially when it comes to the reason technologies, like in terms of you know, front end, like React angle. We have a good support from the, you know EAM side like single pay powers, Adobe. So that makes sense.

Pros and Cons

As a developer. I can say a few things. Like the first good thing which we like when moving to AEM when as an author, like when they enter the content, they can see the live copy there itself, which it was not happening with the previous CMS system. And it's really cool. Like in terms of what to say, the package upgrade, like service pack, upgrade it's keeping the application alive. I mean the downtime which we face as part of the EM is very less impacted.

The CMS we are using earlier, I feel more comfortable the AM now, but pointing out counts I'm really not getting anything into mind right now.

Return on Investment

Definitely it'll be like in the long run, it makes the author job easier and the publishing happens in an instance and the downtime as I told, it's very low on compared of that. So all these factors are the positive side of that.

Usability

Sometimes I like the UI of that, it can be little better like some, there are some areas where it can improve, especially when I navigate to find some page the search part of that so these things can be improvised in the terms of UI when it comes to the. So, again when I do some kind of publishing a few options, like it's not that entity where I can easily grab it. So that's the reason

Favorite Features

The Spark approach, the first of all Atlas, cms, which provides the data for, you are able to use kind of, or one way it's you are getting the data and getting implemented for all the devices, whatever they want, irrespective of that way the spa approach is much, much useful like and it's getting know, supported for all the new frameworks which are coming in like next JS or whatever, no server side. So that is a good side of spa and core components. few core components which are like, always if it is suitable, we'll go for it. Otherwise, obviously we'll customize it. I'm coming to the dam asset management system. It's really cool, especially today we came to know about the Firefly, so the way how the images we can get easily placed. That's really cool.

Key Insights

Do you think Adobe Experience Manager delivers good value for the price?

Not sure

Are you happy with Adobe Experience Manager's feature set?

Yes

Did Adobe Experience Manager live up to sales and marketing promises?

Yes

Did implementation of Adobe Experience Manager go as expected?

Yes

Would you buy Adobe Experience Manager again?

Yes

Likelihood to Recommend

Like to use the software and then maybe some scenarios where it's not quite good, like not appropriate to host more pages like if you have a huge content, especially when it comes to the managing the assets like images or the other stuff, we have one stop solution, where we can get everything in one place. That is a good thing. I mean where we can go for Adobe products. The negative side, like I don't have anything in my mind like, which I can right now. I couldn't recall anything.

Adobe Experience Manager Review

Overall Satisfaction with Adobe Experience Manager