AEM Mobile On-Demand
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 .
AEM provides several tools that enable you to integrate your content into mobile applications.
The following diagram illustrates how the various components of AEM Mobile and On-Demand Services fit together to deliver content to mobile apps.
AEM Preflight app can be considered a testing environment to preview the app and content prior to publishing; whereas the AEM Mobile App is the final app that is built for distribution.
To learn in-depth about Preflight app, see Using the AEM Preflight app in AEM Mobile On-Demand Services Help.
In the diagram above, the AEM Publish instance is not required for a typical deployment scenario to AEM Mobile On-Demand Services.
Starting a New Mobile App
AEM Mobile is just one pillar that makes up the complete AEM platform.
Starting a new AEM Mobile app experience requires a cohesion of roles before it is ready for content editing. The following roles provide a a starting point for creating a new AEM Mobile application:
Before working with AEM Mobile and following the steps within this getting started guide, users should be familiar with AEM. Learn the basics of AEM here .
Understanding the AEM Mobile Application Dashboard
Before understanding the roles and responsibilities, the user should have throrough knowledge of AEM Mobile Control Center or the Application Dashboard . Click here for an in-depth understanding.
An AEM administrator is responsible for adding a new application to the AEM Mobile catalog, either by creating a new app using the creation wizard, or by importing an existing application. AEM administrators who create a new app using AEM Mobile's creation wizard typically select one of the desired app templates either from our out-of-the-box reference samples or (in most cases) a custom app template created by AEM developers.
An AEM administrator is responsible for the following tasks while creating an app using AEM Mobile On-Demand Services:
To get started with an Administrator's roles and responsibilities, See Administering Content to Use AEM Mobile On-Demand Services .
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:
To get started with Developer's roles and responsibilities, See Developing AEM Content for AEM Mobile On-Demand 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.