Share your experience using Adobe Experience Cloud

We use Liferay Digital Experience Platform for a lot of use cases. We have implemented it in oil and gas, manufacturing, petroleum, oil and gas manufacturing, heavy industries, governance, and e-governance.

The most valuable features in Liferay Digital Experience Platform are out-of-box features such as document management, low-code no-code capability, and client extensions. These are very good features of Liferay Digital Experience Platform.

I have utilized the content management feature in Liferay Digital Experience Platform, which is very good and user-friendly. Any layman can use the content management feature.

Liferay Digital Experience Platform has helped us optimize our digital presence and deliver rapid application development. Every customer is happy, and they are giving us repeat orders for whatever we have delivered on Liferay Digital Experience Platform.

I would like to see improvements in Liferay Digital Experience Platform where each feature can be loosely coupled, so I can drag and see what can be used instead of bundling the entire application. If this is possible, that would be great.

There are specific features missing at the moment regarding more integrator and LLMs, and BPM is also present. If one or two LLMs could be integrated, it would be beneficial.

I have been working with Liferay Digital Experience Platform for almost 10 to 12 years.

Regarding stability and performance, Liferay Digital Experience Platform is stable. The current version is good, but one problem is with objects where the load takes much time if the records are increasing. If there are 10 million records, then there is an issue.

With the PaaS, scalability is self-explanatory, and with the on-premises deployment, it is scalable.

My knowledge about Liferay Digital Experience Platform technical support is that there is L1, L2, and L3 support. The mail and voice support is good. The people are knowledgeable and can help with certain issues.

Positive

Before Liferay Digital Experience Platform, I used other solutions such as Drupal, PHP, and Aqua. I have experience with other platforms.

My experience with the setup process was very straightforward.

I have seen a good return on investment with Liferay Digital Experience Platform. We have reused the same kind of model in many places and have reaped the return on investment.

Regarding cost associated with Liferay Digital Experience Platform, it is a core-based application; servers are core-based systems. In India, it is a very competitive pricing market as other platforms are competing with Liferay Digital Experience Platform. AEM and other platforms are also in the market, so the pricing should be factored according to the Indian market.

The key differences that prompted me to switch to Liferay Digital Experience Platform are many. A lot of features such as workflow management and document management are absent in other platforms. The frameworks on PHP and Java are more reliable and open-source where the Liferay Digital Experience Platform application is built on.

I decided to go with Liferay Digital Experience Platform after evaluating many other options and solutions in the market. We found Liferay Digital Experience Platform more comfortable according to our customer requirements and as a digital experience platform.

The main benefits that Liferay Digital Experience Platform brings to the table are numerous. First is rapid application development and many features. Features such as content management and document management make your life easy; workflow management is also present. Workflow can be designed and derived. Form development and everything is very smooth and easy to deliver to the end customer, and you can find many features in one box. You have blogs, wikis, and everything with out-of-box functionality.

My experience with actionable insights is positive; they help in refining content strategies. The content creation is helpful. For external content creation, I use headless CMS APIs for Liferay Digital Experience Platform, and headless APIs for content creation are also available.

My thoughts on the integration capabilities are that integration is seamless. You have headless APIs where you can integrate seamlessly with any other application such as LDAP or SSO, or you can also integrate with different external systems. You have an SAP connector; everything is available.

Liferay Digital Experience Platform's open source flexibility has helped in customizing functionalities for the specific needs of my customers as it is a highly flexible application that can be optimized.

My advice for other organizations considering Liferay Digital Experience Platform is that if it's available, we need to improve on the performance, which is currently what we are seeing. Otherwise, earlier Service Builder was acceptable.

On a scale of 1-10, I rate Liferay Digital Experience Platform a 9.

I am on the Digital Asset Management team and we coordinate projects through Workfront, tracking assets through Workfront and with Adobe Experience Manager.

My use cases involve migration within Digital Asset Management teams. At a healthcare company, the Digital Asset Management team retail, within marketing and an insurance company that was acquired by the company, their digital asset management team within the insurance company coordinated with us as they were also using Adobe Experience Manager. There was a migration of assets from their system to our DAM system. We had about a thousand customers, most of those internal creatives, but some of those are external vendors and photo studios. Vendors would submit assets in the inbox within Adobe Experience Manager, and then I would approve and publish, work on folder structure, naming conventions, metadata, and metadata fields and forms.

The search capability in Adobe Experience Manager is superior, as search capabilities are determined by the metadata. Adobe Experience Manager is the tool for metadata, and it also has metadata automation using AI.

There are some issues with AI in assigning metadata, for example, for stock photos. After some of the AI metadata is assigned, we have to go through and double check to make sure that the AI metadata is correct because sometimes it was not accurate.

The benefits I see from using Adobe Experience Manager are that it's an alternative for a digital asset management system. Adobe Experience Manager tends to be the standard, one of the major options for a DAM tool, and in that way, it's beneficial because it's a mainstream product in the industry.

Improvements could be made, though it's difficult to pinpoint because Adobe Experience Manager has been part of my world for the past several years. Many people complain about the price as it's one of the most expensive tools.

I think it might be worth the money for large companies, and I think large companies are going in that direction, but for smaller companies, it would probably not be worth the money.

I have been using Workfront for about a year.

Regarding stability, there are sometimes bugs, and currently at a beauty products corporation, it seems to be better in general.

The scalability of Adobe Experience Manager is pretty good because we have so many engineers that are knowledgeable about and have experience in altering the Adobe Experience Manager system.

My company has a partnership with Adobe. There are Adobe engineers, sales representatives, and engineers assigned to Sephora North America.

Positive

It's been years since I used a different solution. When I worked with a manufacturer, I used Extensis.

My company has a partnership with Adobe with engineers and sales representatives assigned to a beauty products corporation.

I would recommend it to large companies with a big budget, and I would recommend it to digital asset managers with experience in Adobe Experience Manager because it would be good for their career.

On a scale of one to ten, I would rate Adobe Experience Manager an eight.