The term “Digital Experience” is on everyone’s lips these days. For ethinking, digital experience means when people from a wide range of disciplines can be effective in sharing digital products. Too often, however, digital work ends in the creation of a ticket to the IT department and rounds of requirements or coordination.

Who has not experienced it? An element on the company page is to be placed differently, advertising is to be deactivated for a short time, or a list of articles is to be populated differently. You could do it quickly if you could just do it without software developers.

With the XP Layer you add this Digital Experience to your platform – in the future you can do it easily!

In short – the “Head” is the “face” of the platform. It is what the end user sees and uses. For example, it is the website or the app. A headless platform no longer cares about how the content and data is displayed, it simply provides it through an interface, creating better opportunities to query it right away as you need it as a website or app developer.

This is becoming necessary because the playout channels are becoming increasingly diverse. Example: While an app developer can include fragments of the website in his app for display, an Alexa Skill developer for the Amazon Echo devices cannot do anything with HTML and JavaScript.

That’s why headless platforms deliver their content in JSON or XML format and the end devices read the data and take care of displaying it accordingly – as voice output, website or app.

With the XP Layer, you rely on a standardized content orchestration software where you use widgets to centrally control the content of your platform across all channels. This includes not only texts and images, but also, for example, advertising formats adapted for the respective playout channels. Agile work
is now also possible for all departments with the XP Layer. Editors, product managers, and other stakeholders can centrally control websites, apps, and other digital playout channels regardless of the functionality of their content management system, and can also connect to all conceivable sources. Not only can different CMS systems be used in parallel as sources for your digital products, but other external sources, such as microservices and special importers, can also provide data for your playout channels. The XP Layer thus acts as a kind of “control center” for all the content of your digital products.

With XP Layer, you can focus on your business goals and content, and not waste time and money on technical challenges. This allows you to use your freed-up IT resources for the development of new, innovative products and features. When you use the XP Layer, you are not opting out of systems you already have in place, but ensuring that you become more agile: in the selection of your sources, in the design and control of your playout channels, and also in the development of your features and thus the further development of your platform.