What is the Applause SDK?

The easy-to-install, integrated Applause SDK closes the feedback loop between developers and testers in pre-production, and developers and their users in production.


  • OTA build distribution
  • In-app bug reporting
  • Real-time automated crash reporting
  • Real-time user session reporting
  • In-app user feedback

Supporting iOS  and Android apps,  the Applause SDK is also fully integrated with the Applause Testing Services  Dashboard, publishing  both session and crash reporting into dedicated dashboard modules, and logging bug reports and user feedback in Applause’s bug tracking system.

Note: Through the Applause Testing Services  Dashboard integration, bugs captured by the SDK can also be pushed to third party bug tracking systems like JIRA or MANTIS.

For additional information, see: http://www.applause.com/sdk

Registering an App for Build Distribution

First, login to the SDK panel via:  http://sdk.applause.com

To upload a new app, click on the app name button in the upper right-hand corner of the screen. A drop down menu will appear. Click the “+ Add New app” button.

After you’ve created your app, you can then:

  • Use the  Builds icon to upload a new build.
  • Use the  Teams icon to add additional team members or testers, and organize them into groups (if desired)
  • Use the  Distributions icon to use the SDK’s OTA distribution feature.


Security Management and Controls


Applause well understands the need to protect IP as well as product and brand integrity. It is because of this that we have implemented a number of security management measures and controls into the Applause SDK. Working together, the Applause SDK ensures that project and testing managers have full control over who has access to their mobile app builds and who doesn’t.


All client/server communication is done via the https protocol. This includes the uploading and downloading of builds that have been instrumented and distributed with the Applause SDK.

Role Based Security

The Applause platform supports role based permission levels. This ensures that not only do Applause clients only have access to their data, but it also allows clients to control who has access to specific data and platform features. Those roles are:

  • Owner: Can change project settings and invite additional collaborators. Owners receive all platform notifications by default.
  • Collaborator: Can create test cycles, triage bugs, and communicate with testers and the project management team. Collaborators receive limited platform notifications.
  • Viewer: Read-only access. Viewers can monitor test activity, but can not create or modify test cycles themselves.
  • Testers: Testers are first segregated by platform. Testers log into their own platform which is separate from the main testing services platform. Testers never have access to Applause client accounts. Testers are also only allowed to see test data from the test cycles to which they’ve been invited, that they have accepted invitations to.

Distribution Controls

Email links used to access builds are one time use only, per email address. Once a link associated with a specific email address has been used, it is deactivated and becomes non-functional. This prevents testers from forwarding download links and giving access to mobile app builds to non-approved parties.

Build Version Control

The Applause SDK offers project and test managers build version control through the implementation of a built-in ‘kill switch’. To access this kill switch, an approved user need only log into their sdk.applause.com account, access the Builds tab, and click the ‘Enable/Disable’ toggle for the build they wish to disable.

The flow for build management is as follows:


What happened to Apphance?

Nothing! It’s simply now known as the Applause SDK.

When uTest rebranded as Applause, the Apphance SDK reporting was integrated into the new, unified  360o  Applause dashboard. To better communicate the integration of Apphance into the larger Applause whole, the Apphance brand was retired, and the industry leading solution for real-time session and crash reporting and OTA build distribution was renamed the Applause SDK.

Note that in many support articles there may be references to code snippets or libraries that include the ‘Apphance’ name. Use the given code snippet or library name as written. Names and code will be updated when needed, and support articles will be updated to reflect those changes at that time.

What kind of data does the SDK provide to developers?

To learn more about  the Applause privacy policies: Click Here

The Applause  SDK provides real-time event reporting within the Applause 360o dashboard.

Sessions: Offers a real-time view of testing sessions as they occur. This module provides information on testers, devices, locations, and more. “Sessions” begin when a user starts or wakes an application, and they typically end when the application crashes, when the device announces that a new session has started, or after 48 hours have passed with no new activity.

Crashes:  Provides diagnostic information including timestamp of the crash, stack trace, logs, device conditions and system information.


Additionally, it’s possible to drill down further into the data by clicking within each module.

The kinds of data reported to the Applause SDK  depend on whether or not the person using the app is a pre-production tester or a production user.

Pre-Production Testers

The Applause SDK  gathers the following kinds of non-identifying information:

  • Network Status
  • Power Information
  • Screen Orientation
  • Screenshots
  • Information About the App State
  • System Information
  • Telephony Status
  • Detailed Location Status
  • Unique Device IDs (if available)

Production Users

The SDK  gathers a far more limited amount of information from production users. In general, this information is only gathered when the user sends feedback or when the app crashes. The following non-identifying  information is gathered:

  • Network Status
  • Power Information
  • Screen Orientation
  • Information About the App State
  • General Information About Location (if enabled by the user)
  • Hashed Device ID (if available)

The following information is  NEVER  gathered by the Applause  SDK from production users:

  • Unhashed Device IDs
  • Screenshots
  • Device Name
  • Exact Location
  • MAC address, SSID, or other identifying network info

Please note: that you can use the Applause  SDK to manually log additional information about the app, including any of the information that the Applause  SDK does not gather on its own. If you manually configure the Applause  SDK to log additional information, Applause is not responsible for the privacy implications of that information.