Configuring Native Mobile Applications

Prerequisites

You are assigned the Content Admin role.

You can launch native mobile applications in portal on device, from the Toolbox , Launcher , Favorites , and Portal Explorer .

To launch a native mobile application, you create an iView using the following iView template: Mobile Native Application Launcher iView .

In this iView, you define the properties of the application. Then, you add the iView to the relevant mobile roles.

When the end user launches the application, a landing page appears, enabling installation of the application, if it is not already installed.

In the portal, navigate to Content Administration Portal Content Management .
In the Portal Catalog, select the folder in which to create the Mobile Native Application Launcher iView .
From the context menu of the folder, choose New iView iView from Template .
From the list of templates, select Mobile Native Application Launcher iView , and choose Next .
In the Object Name field, enter a name for the iView, and choose Next .

Specify values for the following properties:

Property	Description
Application URL Scheme	URL scheme for launching the application. For example: `fb://` (Facebook); `twitter://` (Twitter); `mgc://` (Google+)
Application URL in Store	URL in the device store (such as App Store, Google Play) for installing the application. For example, the URL will look similar to: `https://itunes.apple.com/us/app/<name>/<id>` (App Store) `https://play.google.com/store/apps/<details>` (Google Play)
Icon URI	URI of the icon to display for the application.
Filter ID	ID used for filtering entry points according to the portal desktop in use. The Filter ID is relevant only when the Mobile Perspective is Toolbox .
Mobile Perspective	Mobile context in which to display the application. For this iView, select Toolbox if you want to access the application from the Toolbox , or None if you want to access it from the Launcher , Favorites , or Portal Explorer .
Entry Point	Select this checkbox, as required by the intended use of this iView. For example, for use in the Toolbox the iView must be an entry point, whereas for use in the Launcher it must not be an entry point.