Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Using SAP Mobile Place as your app deployment solution

One of the primary goals of the mobile service for SAP Fiori is to provide an integrated solution, one that can support multiple personas, and where the transition from one persona to the next is integrated and effortless.  With the October release, a developer can create/extend a Fiori app and trigger a package app build by leveraging the Fiori mobile cloud build service.  That app automatically gets an enterprise app store entry created.  An app store administrator can complete the decoration of the app store entry and start the app approval workflow.  By decorate, I mean adding things like an app store description, screenshots, supporting documents and videos, etc.  The app promotion workflow starts with an app in "New" status, then can be promoted to either "Trial" or "Production".  When a new version of an app is built, the "Production" app can be "Retired", making room for the new version.  See below an example of a the app promotion actions available to an App Publisher.  Due to his role he can only request that an app be promoted, he cannot trigger the promotion himself:

There is a benefit to this integrated process that is often overlooked.  That benefit is simple - transparency.  In a less integrated model, a developer would build the app and then transport in some manual manner, either through a file share or a content management solution with the person deploying the app.  The person receiving the app, without additional tools, really has no insight into the internals of the app.  He has to trust that the developer has not, willingly or willingly, inserted malicious code.  In the Fiori mobile model, since everything stays completely within the confines of the service, this is not an issue.  The publisher really just needs to trust the process, and trust SAP.  He knows whats in the app because all the metadata used to build the app is available to him within the context of the solution.  BAM!

When the app is put into production, it will automatically be discoverable by an end user accessing our end user enterprise app store, better known as SAP Mobile Place.

Some folks may not know what Mobile Place is, so let's take a moment and discuss.  Simply put, SAP Mobile Place is SAP's mobile enterprise app store.  It's completely customizable, localizable, brandable and many other "ables" that I haven't thought of yet.  It supports ratings and feedback, supporting documents and videos and runs on iOS, Android and Windows Phone 10+.  It supports the distribution of commercial app store, enterpise, Fiori Mobile apps as well as WebURLs/WebClips.  SAP Mobile Place is an integrated component of the mobile service for app and device management and a somewhat lighter version is included in the mobile service for SAP Fiori.  By lighter, I mean that only Fiori mobile apps and only supports unmanaged deployment.  Below is a screenshot of a customized screenshot of SAP Mobile Place, branded for a fictional company called "Bamboo":

SAP Mobile Place (shown with full enterprise app store capabilities)

There is an additional benefit of using SAP's solution from end to end.  By using SAP Cloud Platform services as building blocks, transforming SAP Mobile Place from an unmanaged, single purpose app store (in support of Fiori mobile) into a full featured, fully MDM enforced enterprise app store is almost effortless.  Simply add the subscription, enroll devices, and the apps can be deployed via MDM protocols.

For folks that are looking at mobilizing Fiori, and who are also in need of an EMM solution, these two solutions together can be a very wise choice indeed.

But EMM solutions are not new, and many customers have already implemented a solution, already have devices enrolled.  How can Fiori mobile interoperate with my existing solution?

There are a couple different options here, and they are covered in Part 3 of this series.