AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
Adobe recommends using the SPA Editor for projects that require single page application framework-based client-side rendering (e.g. React). Learn more.
If you are not using AEM as your content managment source, see AEM Mobile On-Demand Services Help.
Before working with AEM Mobile and following the steps within this getting started guide, users should be familiar with AEM.
To Set up your environment for AEM Mobile On-Demand Services, see AEM Mobile Application Dashboard or the Control Center.
An AEM developer extends and creates custom web templates and components to enable the AEM Author to create beautiful and engaging mobile experiences. These templates and components are not only optimized for the mobile app world; but communicate both to the device and to the AEM server (any remote server) to omni-channel service end-points. AEM’s built-in content editor is used by AEM Authors to create rich and relevent experiences within the app, including integration with the rest of the Adobe Marketing Cloud.
An AEM developer is responsible for the following tasks while creating an app using AEM Mobile On-Demand Services:
See Developing AEM Mobile Content Services for developing Content Services.
An AEM developer’s role does not start and end with the development of templates and components. An AEM developer can create an entirely new app rather than simply extend the out-of-the-box reference implementation sample.
To learn about the roles and responsibilities of an Administrator and an Author, see the resources below: