Managing content is very user-friendly, AEM makes maintenance simple and auto-scalable Area of improvement for Cloud Service: For the last four years, I've been working on AEM as a Cloud Service. I feel the tool has all the features needed for production, but the problem is with skills. Depending on the skill level of the developers building the components within Adobe Experience Manager, you can have a very streamlined implementation or a very difficult one. Tool-wise, the Adobe Experience Manager support team is not very responsive when the user faces issues in AEM as a Cloud Service. If I reach out to Adobe for something, they create a ticket, and then I might wait three to four days for a response. When I have issues, I want an immediate response. On AEM as a Cloud Service, this is the one thing I think Adobe needs to improve. They should resolve issues within a day so everything runs smoothly for the user. Area of improvement for on-premises: For on-premises AEM, everything is managed by us, but since Adobe Experience Manager was not a very big market earlier (though it's growing now), there are limited clients. The cost of the tool is high, and maintenance is heavy – it's very costly. So, the developers working in AEM development might not always have the proper skills to develop the components. For example, in a normal website, we often see carousels which represent your website in a very dynamic way. Now, suppose you have two carousels on the page – one at the top and the next at the bottom. They have different purposes. If I'm a skilled developer, I'll create one component and serve both banners with the same component – a single, dynamic component. This makes it easy for content editors in the production environment to drag, drop, and change the content. But, if I'm not an experienced developer or I don't have knowledge of AEM, I might create two components – one for the top and one for the bottom. Maintenance becomes heavy, and it's harder for the content team to understand which component to use. A less experienced developer might create multiple components for the same function, increasing complexity and challenges. Over the last three to four years, this lack of resources and skilled AM developers has created these kinds of issues.
