Dial Once

Android SDK Specifications

Table of Contents

  1. How it works
  2. SDK Weight
  3. Dependencies
  4. Integrating the SDK
  5. Available platforms
  6. Supported versions
  7. Permissions
  8. SDK Communications

How does it work?

The Dial-Once SDK is integrated in your app and only runs during one of these actions:

  1. Calling a number
  2. Connecting the phone to a power supply
  3. Connecting to the internet

Dial-Once uses these intents to launch itself and to perform tasks such as displaying the customer service interface or updating its local database. Then it shuts itself down and frees up the memory until the next action.

Dial-Once does not run in the background and does not turn your app into a battery-killer

What is the footprint on your application?

Currently (as of v2.6.17), the Dial-Once SDK has a total weight of 180KB.

This is indicative and may change in the near future as we are constantly updating and adding new features.

What are the underlying dependencies?

Current version (v2.6.17) has the following dependency tree:

+--- com.bugsnag:bugsnag-android:3.9.0
|    \--- com.android.support:support-annotations:25.3.1 -> 25.4.0
+--- com.google.code.gson:gson:2.8.5
+--- com.squareup.okhttp3:okhttp:3.12.1
|    \--- com.squareup.okio:okio:1.15.0
+--- io.socket:socket.io-client:1.0.0
|    \--- io.socket:engine.io-client:1.0.0
\--- com.android.support:support-v4:25.4.0

How to integrate the SDK into your app?

Installing the SDK is simple as all you are adding is a single line of code. You can find a more technical explanation on the SDK page.

On which platform is the Dial-Once SDK available?

The SDK is available for Android. iOS and WP8 are coming soon.

What are the supported Android versions?

We support Android API version 9 and more.

Which permissions are required?

We use advanced features of the Android platform so permissions are required:

You do not need to modify your app or add permissions since the SDK does it automatically.

How data is transmitted to Dial-Once?

We only transfer anonymous user data over secured TCP connections (wss and https). As soon as we check that the device is up to date with our database, we put the device to sleep through a socket secured channel connection, and all communications with Dial-Once are stopped for a large amount of time: not consuming the user battery. Each user have a token that can be revoked anytime server side.