Dear friends

This week we will focus on different approaches of exposing SAPUI5-based applications to mobile devices (smartphones / tablets). Please feel free to contact us in case you require any assistance in choosing the right option for your organization!

Exposing as regular website

This is the most straightforward way to access SAPUI5 application – users will navigate to a URL that takes them to your application (in case it’s standalone) or even to your SAP Fiori Launchpad, where application can be accessed through the catalog / tile according to authorizations. This is a classic case of exposing a SAPUI5 application.

 

Pros:

• Simple architecture, the only thing you need to do is to share the correct URL with your users, and make sure their mobile devices have access to internal network.
• Good UI performance as no wrapping / additional components involved
• Easy to debug
• Device and OS agnostic

Cons:

• Browser address bar is visible
• No access to native device capabilities (sap.ndc)
• Users will have to know the URL all the time
• In case URL changes you need to deliver it manually to users

Exposing as a Web App

In such a case a user will access your SAPUI5 application from a mobile device home screen, which will feel & look like a native app, although this scenario utilizes a built-in device web browser and launches a URL.

Pros:

• Better and more “native” user experience
• No URL address bar
• Good UI performance, although depend on built-it device browser
• Easy to debug
• Device and OS agnostic

Cons:

• Distribution of such a “hybrid” app is either manually or MDM-based
• Additional settings for JS might be required
• No access to native device capabilities

Exposing through SAP Fiori Client

Users will access the SAPUI5 application through a generic native application called SAP Fiori Client, which is available through AppStore and Google Play market. The application is a hybrid wrapper for your application / Fiori Launchpad and provides additional native capabilities, such as built-in barcode scanner.

Pros:

• Access to native device capabilities (sap.ndc)
• Hybrid app user experience
• Supports iOS & Android

Cons:

• Lower UI performance due to hybrid overhead
• Application cannot be branded according to organizational requirements
• Distribution is required through MDM tools
• Inconvenient to debug & support

Exposing with SAP Mobile Services

This way of exposing a SAPUI5 application is very similar to generic usage of SAP Fiori Client, but includes ability of branding & organization settings.

Pros:

• Access to native device capabilities (sap.ndc)
• Hybrid user experience
• Branded application
• Supports iOS & Android

Cons:

• Additional licensing required
• Lower UI performance due to hybrid overhead
• Distribution is required through MDM tools
• Inconvenient to debug & support

Exposing a native custom application by using mobile UI5 libraries (Mobile SDK)

This scenario assumes a native development of platform-specific application that utilizes mobile development kits.

Pros:

• Better performance
• Better user experience
• Access to native device capabilities

Cons:

• Complex development cycle
• Native development knowledge required
• Distribution is required through MDM tools
• Complex support matrix (device & OS level)
• Inconvenient to debug & support

Summary

In case you have a request to deliver SAPUI5 applications to mobile devices – make sure you outline all aspects of your requirement and possible solutions, while taking into account both advantages & disadvantages outlined above! Feel free to contact us in case you would like to have a brainstorming over your specific SAPUI5 requirement.