At Adobe, we understand that content is the life blood of customer experience. Now that our world is more connected than ever, it is important to be able to quickly create and reiterate customer experiences, and a big part of that is making sure customers receive the right content across the entire customer journey. App-like and immersive experiences are now a must, and at the center of this effort are developers.
However, developers are struggling to deliver cohesive content across every touch point (modern web, smart watches, native apps, etc.). That is because until now, content has been siloed and difficult for developers to easily access to create new app-like experiences that meet consumer expectations.
Today, at Adobe Developers Live — Adobe’s virtual conference dedicated to bringing together digital experience developers — we announced new Adobe Experience Cloud capabilities that provide developers best-of-breed tools to create and manage experiences. Specifically, new headless content management system (CMS) capabilities in Adobe Experience Manager to help developers seamlessly deliver content, plus the new updates to the Commerce Integration Framework (CIF) allow to create shoppable app-like experiences that combine content and commerce.
Adobe Experience Manager as a Cloud Service, part of Adobe Experience Cloud, is the industry’s most advanced cloud-native solution for digital experience management and brings together rich out-of-box capabilities and content customization options that marketers and developers demand, combined with SaaS-like agility.
New headless CMS capabilities in Adobe Experience Manager
To allow developers to easily fuel content into multiple touchpoints, we are introducing GraphQL APIs for headless content delivery. GraphQL, an industry standard, application-agnostic query language to retrieve content, lets developers get exactly the content they need — nothing extra — so that content matches the needs of their app. Additionally, queries can also return all nested content in a single call. Because fewer requests are being made in both directions and less bandwidth is being used, overall app performance improves.