Digital transformation is everywhere. In Covid times, entire businesses had to pivot in weeks, if not days. What used to be considered convenience features, became critical services.
Developers were there to rally for the cause, to virtually connect family, friends, coworkers and businesses; keep workers employed and business afloat.
To support developers with this accelerated pressure, the developer experience organization, or DevX for short, was formed within Adobe with this ambitious aspiration:
empower and support the world’s best Customer Experience Management (CXM) community, ecosystem and platform.
DevX in the Adobe Experience Cloud
The Adobe Experience Cloud (AEC) began as a series of acquisitions. Who amongst us recognizes some of the old pre-acquisition names like Day Software, Neolane, Omniture, Satellite or Livefyre?
The need for a more seamless integration was apparent and much has changed since the old days. Adobe has spent enormous effort and work in the area of usability and API integration to unify the different solutions under the single heading of Adobe Experience Cloud. However, Adobe is far from finished. There is more work to be done to unify the developer experience and capabilities across all the available Experience Cloud solutions. Development stacks, methodologies and tools differ between solutions within AEC which results in context switching between solutions and sometimes requiring a steep learning curve.
DevX aims to bridge that gap, providing Experience Cloud developer tools and services to reduce the switching of development stacks, methodologies and tools whilst opening up deeper webhooks for extension and customization by developers.
To unify all the different Experience Cloud solutions in terms of development capabilities, the ‘Experience Cloud Unified Shell’ was built. All the solutions inside the shell have an API and SDK that can be accessed in a consistent manner. Additionally, the Experience Cloud Unified Shell also includes a connection client.
A command line interface (CLI) was built for easy interaction with before mentioned ‘shell’ and SDKs. This is where ‘Project Firefly’ comes into the picture.