Adobe Experience Manager Mobile Community is a place to ask questions and learn from Adobe’s experts, customers and expert developers like you. We've gathered a group of practitioners and Adobe experts right here on the community for you. We have product managers, evangelists, engineers, consultants, and support agents all here in the community from the Adobe side. We've also got industry practitioners here from all backgrounds and skill levels.
First things to do: Go ahead and Introducing yourself and know your peers.
When you purchase a license to Adobe Experience Manager Mobile, you have access to Adobe Experience Manager Mobile On-Demand Services (AEM Mobile) and to Adobe Experience Manager (AEM) instances as defined in the license agreement.
Adobe Experience Manager provides an environment for authors to create and manage content for mobile apps, without involving IT or designers in day-to-day operations.
The license agreement for AEM specifies the number of instances that can be deployed in a production environment. You can set up and maintain Experience Manager instances specifically for use with AEM Mobile, or you can license existing Experience Manager Sites or Assets instances for use with AEM Mobile.
The AEM Mobile On-Demand Services provide the following capabilities:
Getting started with Adobe Experience Manager Mobile
Getting Started: External link: https://helpx.adobe.com/digital-publishing-solution/help/getting-started-dps.html
Still have Questions?
You're already in the right place. Start posting your questions in our dedicated Adobe Experience Manager Mobile community (URL to this community). Remember, no question is a "dumb" question. If you have the question, there are likely three others with the same question.
I understand there are two ways to develop the Hybrid app in AEM
What is the actual motive behind facilitating two ways?
I see in current out of the box components available ng-components and ng- page, all the scripts have in build support to develop the hybrid app using AngularJS.
Is there future any plan to Adobe to update these out of the box components support to latest Angular frame work and continuing support for developing Hybrid Apps using AEM alone rather AEM mobile cloud?
I am using AEM 6.4 and want to build an AEM Mobile on demand App and manage its contents using AEM 6.4. With 6.2, i could create a new AEM Mobile On Demand App and connect it to AEM Mobile On demand services portal. I have configured a new AEM On Demand Configuration already(with API Key and Secret from wwds support) as a cloud configuration, however i do not see template to create an On demand App in 6.4. I saw that Adobe have taken out Mobile console from 6.4 and there was a recommended package to be installed from Package share. I have installed that package, though i can see Mobile console and an option to create an App now, but i guess the recommended package does not have template to create On Demand App.
Do you know if we can use AEM Mobile with AEM 6.4 through additional feature pack installs. Otherwise what is the recommended way to manage contents for On Demand Apps from AEM 6.4.
AEM Mobile on-demand services is only supported via upgrades.
ie: you have an existing app build using AEM 6.2 or 6.3 and upgrade to AEM 6.4.
You cannot create and manage new on-demand apps in 6.4.
Thanks for that reply. Understood but i am surprised. Does that mean that if i am a new Adobe customer starting on AEM 6.4(which is the case for one of my clients), i cannot create or manage AEM Mobile apps through my AEM instance. I am wondering if that is true, why Adobe has gone down this route. Is this a deliberate step in AEM Mobile product roadmap trying to kill AEM Mobile On-demand service. Sure, i can still create new Apps directly in on-demand portal but one the really powerful features that i was thinking was to be able to manage contents for those using AEM as i could reuse lot of my content from AEM web channel. Do you have any materials/product roadmap to explain this step and future of AEM Mobile.