Mobile App

  • 3 minute(s) read
Prev Next

In order to be always connected with your products, other than from a browser, the tenant application can be accessed from a Mobile App, providing your users with a more complete user experience.
The mobile experience can be tried out in preview on your tenant by using the Servitly App. Then, decide whether to keep using it in a branded version or develop your own mobile app using the Servitly API.

Servitly App

On the app stores (Apple and Android), you can download the Servitly mobile app.

The Servitly mobile app is available for the following platforms:

Once installed and launched, by pressing the add button, you can register a new tenant to access.
To register a tenant, you have to provide the name of the tenant (e.g. acme), and whether it is in the Sandbox environment.

When a new element is added to the app's main page, and by clicking on the tenant box, the page switches to the tenant application.

Mobile Features

The navigation within the mobile app is integrated with the device's hardware, for instance:

  • Product activation can be done by using the camera to scan the serial number from a barcode or QR Code

  • The GPS position is automatically used as the product position when activated.

  • Bluetooth for device configuration (e.g., Wi-Fi access or other settings) can be used.

  • Level-based parameters can be updated by using a Knob.

  • Alerts can be notified by using push notifications (available for the branded version only).

Branded Version

You can use the default Servitly mobile app in a branded version. The branded version will have its own icons and automatically start on the configured tenant, without any additional registration step.
The Branded Default App, which is a customization of the Servitly Default App for a specific tenant, is an app based on the Cordova framework, so it is not a native APP.
The advantage of using this app is that any update to the tenant configuration (e.g., a new dashboard) is automatically available to your customers, without the need to update the mobile app on the stores.

You can ask your CSM (Customer Success Manager) or write to support@servitly.com for more information about the branded Servitly Mobile app.
The publication on the stores (Android and iOS) is up to you, as the store account is headed to you. So you are responsible for defining the store contents (images, descriptions), and compile questionaries (e.g., GDPR, PEGI).

To let us build the application, we need the following information and resources:

  • The name of the application (e.g., ACME Connect) that is visible in the store and in the launch menu.

  • The application identifier (e.g,. com.acme.connect).

  • The API Key, which is configured in the Console API Keys page.

  • The 512px X 512px icon, which is used in the application splash screen.
    You can find a complete icon design guide here. The same icon will be used for the iOS version.

  • The color (e.g. #009EF7), which is  used in the application splash screen as background.

Certificates:

  • Android: A self-signed certificate (JKS) with your company details is used to build the application.

  • iOS: To build the application, you must provide a certificate (p12 format) with a passphrase and the provisioning profile.
    Both certificates must be available for DEVEL and PRODUCTION.

Notifications:

  • Android: configure the Android Push plugin and provide the Private Key JSON file.

  • iOS: In the Apple Console, configure the Push Service certificates and use them to configure the iOS Push plugin.

Encryption Usage

The target app store may request more details about how the app uses the encryption.
Below you can find more details about possible questions.

  • Does your app use encryption? → Yes

  • Does your app use only standard encryption? → Yes

  • Is the encryption limited to authentication or secure communication? → Yes

  • Does your app use any Apple API?  → No

  • Does your app qualify for an exemption? → Yes (5D992.c)

  • How does your app use encryption? → Encryption Usage Description Document
    The application uses encryption exclusively to secure communications between the app and its backend servers.
    All data transmitted over the network is protected using standard HTTPS connections based on TLS.
    The encryption mechanisms are provided by the phone's operating system and/or third-party networking libraries that rely on standard TLS protocols.
    The application does not implement any custom or proprietary cryptographic algorithms, nor does it perform custom key management.
    Encryption is used solely for secure data transmission, authentication, and protection of data in transit.
    The application qualifies for the export compliance exemption under U.S. regulations (5D992.c).

Custom Mobile App

If you are especially demanding in terms of user experience, and you need to create a native app, you can do it by leveraging your preferred framework and the API provided by Servitly.