Adobe Experience Manager Review
September 11, 2023

Adobe Experience Manager Review

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Adobe Experience Manager

The main use case scenario is to create a very user-friendly drag and drop interface to build and maintain websites so that a non-technical, non like software focused user, someone that has like a marketing degree can maintain an operating large scale enterprise website with like minimal involvement. so I'm there to build custom components, custom features any kind of like optimizations that, or any sort of like improvements that I get under the hood to kind of improve services so then someone can come in and say, we need a new page, we have new product. And all they need to know is what that new page should look like and what the product should be. And that's all the experience they'll need and everything else should just work. and they can deploy that out to multiple languages, multiple different countries. it can do translation, it can do all that sort of things for you automatically. so you can maintain and operate this giant scale site with a smaller core team of individuals.
  • I think some of the strengths really are that kind of ease of use of drag and drop. Once you have a developer come in and really customize the application to like what a client specifications are after that point you really can lay back on the development work and really rely almost entirely on the, what Adobe calls the authors to actually build and maintain these websites. And they really have thought of a lot of those edge cases where things can break. So everything is kind of, I don't wanna say idiot proof because authors are smart but it's made in a way that you can't really make things too wrong and that in with whatever you're building, it's always up to the brand standards. It's up to the accessibility standards. So whatever they're building is ADA compliant and things like that. So everything that you're doing is still maintaining a proper website, which under the hood websites are incredibly complicated involved so many different technologies. So to be able to simplify all of that to a user is incredibly powerful.
  • From my personal experience as a developer, I think Adobe has a lot of work to do with their documentation. certain things they're very strong and they're very like they detail things out great. Other things that haven't been updated since like 2018 don't work anymore and it requires a lot of trial and error to actually figure out what needs to happen. A lot of the time you rely on other AEM developers inside in the inside the community forums that basically have to say, these instructions don't work, has anyone actually gotten this to work? And other people that have done the work and figured out how it actually works have kind of filled in those gaps. So it's great that those exist but it would be great if those holes never existed in the first place and Adobe's documentation really just was robust enough and didn't have typos and really got refined more frequently.
  • So from my experience, that's definitely where I think Adobe could really improve the work experience because it shortens development time, it makes my work a lot easier, which means I can deliver things way faster and things move a lot quicker because I hate having to say I'm doing it the way Adobe says I should do it, but it doesn't work still so I need to figure out what's wrong. that's not a fun thing to have to talk to a client about because then they get confused and are confused why Adobe isn't working the way it should be. it just creates kind of some tighter timelines and things.
  • So that's something I know a little bit less about as a developer. I'm the one kind of dealing with the smaller details and then I hear about it showing to the client and I hear good reviews and things like that. So I don't actually know of the actual like we've implemented. So some projects are like an upgrade from an older version of an AEM to a new version of aem. I don't know what that upgrade actually turns into a profit margin. but I know a lot of the times those things keep the product like up to date keep the current technology cuz web turnover is so fast. So I imagine the turnover rate is high cuz AEM is not a cheap product and a lot of companies, big brands still use it actively. so I'm assuming that the return on investment is good but I unfortunately don't know the specifics.
I think a little harsh but I'm saying that because I think Adobe can really improve it. There are, there are a few places where you can see Adobe has this great design philosophy for how it should all work together and then there are these like kinks and hiccups that really get really confusing and can disorient people. and especially with working our QA team for example, sometimes they get so turned around by features that as a developer I'm so used to them but to a fresh set of eyes it can be really unintuitive. So I think Adobe has some really good design principles but I feel like they're almost there. There's definitely a, like a lot of times you need to be handhold and be like, this is confusing or this feature doesn't really work the way you'd expect. and I wish there was less of that.
  • Definitely the the editor like the, the main UI for like configuring the pages and the sites in AEM sites I think is very powerful. I think the design of it is pretty smart. I think it's pretty user-friendly and has really has a, a lot of feature rich tools that are designed in a way that make a lot of sense once you kind of get the feel of it. so I really think that's definitely a strong core. one of the features. Could you list some of the other ones just cuz there were a few that I remember liking core components, SBA editor, multi-site management, digital asset management.

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

Yes

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?

No

Would you buy Adobe Experience Manager again?

Yes

A good example actually of is a big business that has multiple sub-brands, like a really large enterprise company that has a lot of sub-brands that are in similar areas. one of the things you can do is you can actually maintain several different websites that all function very differently under the same kind of umbrella and you can even share functionality between those. So if you have similar functionality and your developers are smart enough to think ahead and see the connections, you can really have a system that you don't need to rebuild every site from scratch. You can start kind of building a core that then you share out between all your brands and then if you ha see a bug you fix it in one and it fixes across all of them and things like that. And I feel like the sites that I've seen that have implemented that like large scale multi-site management I think really can leverage that power.