Agentry Client for Android Branding Overview

The Agentry Client for Android can be branded to replace the default, SAP provided logos and application strings. This process includes the use of the Agentry Client for Android Branding SDK, which is a ZIP archive containing the necessary resources to support the branding process.

In addition to this SDK, it is necessary to install the following tools provided by third parties:

In addition to these tools, it may be necessary to register your mobile application to obtain a Product ID and Simple API Key from Google for use with the Google Cloud Messaging (GCM) service. This is needed when it is desired to send notifications to client devices in the event of missed push data. If push is not to be a part of the implementation, or if notifications for missed pushes are not required, this is not needed.

It is also likely you will want to replace the default logos displayed for the application, including it’s shortcut and task bar icons, as well as the logo displayed in the application’s logon screen. These icon images should be created before of beginning the branding process as they are included in the build of the branded client.

It may also be necessary to obtain the services of a translator to localize the Agentry Client for Android. While most values are localized through a different means, and after the application has been developed and tested, there are a small number of displayed strings contained in the resources found within the Agentry Client Branding SDK for Android. These strings are typically displayed when the Agentry Client is started and before the initial transmit.

Overall the following are the main tasks in the branding process:
  1. Perform the environment setup, including: installation of the JDK, Android SDK, Ant scripting utility, and Cygwin; making environment variable changes; and extraction of the Agentry Client Branding SDK for Android.
  2. Optionally, translating strings contained within the contents of the Agentry Client Branding SDK for Android.
  3. Optionally, obtaining a Simple API Key from Google in support of missed push notifications using GCM.
  4. Repackaging the Agentry Client for Android using tools from both the JDK and Ant scripts.
  5. Testing the branded Agentry Client prior to deploying it.