Producing the initial natural Android MobileFirst app

Producing the initial natural Android MobileFirst app


To serve a native Google android program, MobileFirst Machine must be aware of it. For this function, IBM MobileFirst Software Basis delivers a Indigenous API collection, that contains a couple of APIs and design

This training talks about tips on how to crank out the Android mobile phone Natural API and the way incorporate it by using a local Android application. These actions are needed to help you put it to use in the future to obtain tasks such as attaching to MobileFirst Host, invoking adapter operations, applying authentication approaches, and the like.

Prerequisite . Designers have to be adept with making use of Google’s developer tools.

Building a MobileFirst Indigenous API

  1. In MobileFirst Studio room, generate a MobileFirst project and add a MobileFirst Indigenous API.
  2. In the New MobileFirst Indigenous API dialogue, key in the application name and select Google android for those Environment area.
  3. Correct-select the developed NativeAPI folder (positioned in your-jobs/apps/your-nativeapi-app-brand ) and choose Function As Andgt; Deploy Local API . This step is needed for MobileFirst Web server to understand the application form any time a request grows to the server.
  4. The MobileFirst native API has several components:
  • wlclient.houses provides the connections controls that the local Android operating system program employs.
  • worklight-android operating system.bottle is definitely the MobileFirst API catalogue.
  • gcm.bottle and press.png are for Google and yahoo press notice expert services.

JSONStore folder is designed for additional JSONStore assistance in native software programs.

armabi. armabi-v7a. mips. and x86 folders are for non-obligatory App Legitimateness Protection in indigenous apps.

As with all MobileFirst undertaking, you make the machine setup by altering the data files which can be on the server\conf directory.

You use the app-descriptor.xml record to determine app metadata and to set up security configurations that MobileFirst Machine enforces.

  • wlclient.qualities
  • The wlclient.attributes data file holds machine settings qualities which is person-editable.
  • wlServerProtocol – The communication protocol to MobileFirst Machine, which is often sometimes http or https.
  • wlServerHost – The hostname of MobileFirst Server.
  • wlServerPort – The port of MobileFirst Host.
  • wlServerContext -The situation underlying route with the application over the MobileFirst Server.
  • wlAppId – The applying Identification as outlined in the app-descriptor.xml file.
  • wlAppVersion – The application form type.
  • wlEnvironment – Whatever target environment on the local application form.
  • wlUid – Your property made use of by MTWW to determine this like a MobileFirst request.
  • wlPlatformVersion – The MobileFirst Business version.
  • languagePreferences – Number of favored locations.
  • GcmSenderId – This residence specifies the GCM Sender Identification used for force notifications. Automatically, this property or home is commented out.
  • Building and configuring an Android os natural application
  • Develop a indigenous Android operating system app or utilize an existing one.
  • Replicate the worklight-android os.jar. uicandroid.jar. bcprov.bottle. and android-async-http.bottle data files from your WorklightAPI folder to your new native Google android application form, within the /libs directory website.
  • Clone the report wlclient.components coming from the MobileFirst native API folder to your new local Google android application, inside the /possessions website directory.
  • Put the next permissions into the AndroidManifest.xml record:
  • Add the MobileFirst UI pastime:

For additional information, study the “Getting local applications for Android” person documentation issue Following the request is run in Eclipse, the last outcome is a native application which contains the MobileFirst API selection. The given Studio room job posesses a MobileFirst Recording studio project using the produced NativeAPI directory. The presented Natural project contains an Android operating system request presently installation along with the MobileFirst NativeAPI.

Example app