Appian makes it possible for you to work with our Appian Technical Support Team to customize Appian for Mobile Device applications and create a mobile application that displays your organization's logos and a customizable introductory experience.
The process for creating and deploying a custom mobile application is dependent on you as the customer deciding how you want the application customized and then working with Appian to create it. We have divided the process into two main steps:
Depending on the mobile device you want to create the application for, your company needs to meet the following requirements:
NOTE: When a new version of an Appian for Mobile Devices application is released, you must request a new build from Appian Technical Support and repeat the process for building the application. This includes going through the Apple or Android review process if your deployment approach requires it.
The attributes listed below can be customized for your Appian for Mobile Device application. Gather this information in preparation, then proceed to the "Create and Deploy the Custom Application" subsection for the mobile device you want the custom application for.
For iOS applications, the following attributes are also customizable:
Follow the image specifications listed in the subsections below for the mobile device in question:
Create application icons to replace the default icons. The icons will be used as the launch, search results, and settings icon for iPhone and iPad.
|icon-20x20.png||Yes||20 x 20 pixels|
|icon-29x29.png||Yes||29 x 29 pixels|
|icon-40x40.png||Yes||40 x 40 pixels|
|icon-58x58.png||Yes||58 x 58 pixels|
|icon-60x60.png||Yes||60 x 60 pixels|
|icon-76x76.png||Yes||76 x 76 pixels|
|icon-80x80.png||Yes||80 x 80 pixels|
|icon-87x87.png||Yes||87 x 87 pixels|
|icon-120x120.png||Yes||120 x 120 pixels|
|icon-152x152.png||Yes||152 x 152 pixels|
|icon-167x167.png||Yes||167 x 167 pixels|
|icon-180x180.png||Yes||180 x 180 pixels|
|icon-1024x1024.png||Yes||1024 x 1024 pixels|
NOTE: Ensure that your images conform to the iOS Human Interface Guidelines.
Create application logos to replace the default logos below.
|File Name||Image and Placement||Required||Size||Example||Example with Background|
|logo-100x35.png|| Low-resolution logo
||Yes|| 100 x 35 pixels
|logo-200x70.png|| High-resolution logo
||Yes|| 200 x 70 pixels
To enable a Welcome Screen, create background images for it based on the specifications in the table below.
|welcome-640x960.png||iPhone 4s high-resolution||Yes||640x960 pixels|
|welcome-640x1136.png||iPhone 5 and later||Yes||640x1136 pixels|
|welcome-768x1024.png||iPad portrait||Yes||768x1024 pixels|
|welcome-1024x768.png||iPad landscape||Yes||1024x768 pixels|
|welcome-1536x2048.png||iPad portrait high-resolution||Yes||1536x2048 pixels|
|welcome-2048x1536.png||iPad landscape high-resolution||Yes||2048x1536 pixels|
This icon is used to launch the custom application on mobile devices. Create an application icon to replace the default icons below.
|launcher_72.png||Yes||72 x 72 pixels|
|launcher_96.png||Yes||96 x 96 pixels|
|launcher_144.png||Yes||144 x 144 pixels|
|launcher_192.png||Yes||192 x 192 pixels|
Push Notification Icons
These icons are used to represent notifications in the status bar. They should be white and flat (no gradients).
|notification_36.png||Yes||36 x 36 pixels|
|notification_48.png||Yes||48 x 48 pixels|
|notification_72.png||Yes||72 x 72 pixels|
|notification_96.png||Yes||96 x 96 pixels|
Welcome Screen Logo
To enable a Welcome Screen, create a logo for it based on the specifications in the table below and select a background color.
|welcome_bg.png||Yes (if welcome screen enabled)||400 x 220 pixels|
By default, the background color is set by the following property in
Google Play Image
Create a high-resolution icon for Google Play to replace the default icon below.
|Yes||512 x 512|
See the "Graphic assets, screenshots, & video" help page for more information about using graphics and other media on Google Play.
There are three different approaches your company can take to deploy a custom application for iOS. The list below details possible pros and cons as well as detailed requirements of each one.
The approach you select depends on the level of in-house development experience your company has with iOS applications, how you want your users to access the application, and how quickly you want the application to be available.
After you decide on a development approach and meet the requirements listed above, complete the following steps in conjunction with your Appian Technical Support Team. The steps below differ depending on your deployment approach.
VPP Deployment Process
Public Deployment and Enterprise Deployment Process
Custom Appian applications for Android devices are created by Appian and then must be submitted by your company to Google Play for publication or directly distributed by you to your employees.
Custom Appian applications for Android offer the ability to configure two new optional features during custom application creation:
Hardcoded Server URL:
Enabling this configuration will ensure every device using your custom application targets the designated server URL and no other. It also removes a step from individual application setup on those devices.
To configure for your application, provide Appian Technical Support with the server URL you would like to use for all your users’ mobile devices.
The Device Sharing feature is intended for those customers with teams of users sharing a single Android device for their work. The feature enables the team to quickly log in and out of their accounts as needed. Note that mobile push notifications are not available in Device Sharing mode.
Device Sharing requires a Hardcoded Server URL to be provided to Appian Technical Support at application creation time. Custom applications with Device Sharing enabled must have this setting.
You will also need to consider an idle timeout period for Device Sharing. This makes it easier to ensure applications are only accessed by authorized users at all times. For example, if a user is logged into the application when the device goes to sleep for more than the allotted idle timeout period, the application will force the next user to attempt to access the application to authenticate. The timeout can be any increment of minutes you prefer, starting at 1 minute and up to "never." The default configuration is 10 minutes.
To have your custom application created, contact Appian Technical Support and send them the custom attributes. They will create the application and send it to your company once it is complete.
NOTE: App store images (for example, the Google Play icon) are not part of the generated application package and need not be included in the package. Whoever is responsible for submitting the application to Google Play, however, will need those images.
The submission process usually takes between 15-60 minutes. Once it passes submission, it will be available for download by your users.
BlackBerry MDM is supported by dedicated iOS and Android apps, Appian for BlackBerry (formerly called Appian For Good), in the BlackBerry Marketplace.
For most other Mobile Device Management (MDM) vendors, Appian supports application wrapping. A custom mobile application and coordination with the MDM vendor is required. For more information, see Securing Data for Mobile Users.
Contact Appian Technical Support to have your custom application created. They will assist in providing your MDM vendor the necessary files for wrapping.
This section provides a step-by-step guide on how to generate the requisite certificates and provisioning profiles needed for a custom branded Appian iOS app from the Apple Developer Portal.
Create an App Group.
Create an iCloud container.
Create an App ID. Choose an explicit App ID. Enable "App Groups", "iCloud", and "Push Notifications" App Services.
Navigate to your App ID and click on the "Edit" button.
Navigate to the "App Groups" Application Service and click on the "Edit" button. Then add the App Group you created in step 1.
Navigate to the "iCloud" Application Service and click on the "Edit" button. Then add the iCloud container you created in step 2.
Generate a push notification key and provide it to Appian Technical Support.
Create a "Production" iOS certificate, click on the "Continue" button and follow the Apple provided instructions. Download the generated certificate and import it into the "Keychain Access" macOS app.
Create a "Distribution" iOS provisioning profile associated with the App ID you created in step 3. Download the provisioning profile.
Create another App ID. Append ".NotificationService" to the App ID you've chosen in step 3 (e.g., com.appian.example.NotificationService). Associate this App ID with the App Group you created in step 1.
Create a another "Distribution" iOS provisioning profile associated with the App ID you created in step 10. Download the provisioning profile and provide it to Appian Technical Support.
If you have access to a development environment that satisfies the minimum requirements for iOS application development, and feel comfortable running commands from the Terminal (see instructions below), you can sign the .ipa file yourself.
If you prefer that Appian generates the
.ipa file, please provide the following to Appian Technical Support:
.p12 file from the keychain you created when you imported the certificate into the Keychain Access macOS app. Select the contents of that keychain, CMD-CLICK the selection, then Export:
All Distribution iOS provisioning profiles that you downloaded.
This must be done on a Mac.
fastlane tool by running the command from the Terminal:
sudo gem install fastlane -NV
Then, run the following command from the Terminal:
fastlane sigh resign path/to/downloaded/unsigned_appian_app.ipa -p com.appian.example=path/to/profile.mobileprovision -p com.appian.example.NotificationService=path/to/notification_profile.mobileprovision
-pflag and the following argument are omitted. Note that
com.appian.exampleis the App ID that you created above.
When the Available identities prompt appears in the Terminal, copy the coded value listed underneath the identity of the certificate file, and paste it next to Signing Identity:.
Press the Return key and
fastlane will run and sign the
On This Page