Mobile Surveys


In order for your apps to receive and display mobile surveys please integrate with the latest mobile sdks (released late June 2016). Survey support starts on versions 3.7.0 (both iOS and Android). Once you’ve updated you’re ready to start using Mobile Surveys!

Surveys are set up via the web panel and presented to a participant while they’re using your app.

Setting up a survey


In the left hand menu click on “Surveys” and then on “Create survey”


You can set the survey Title and Introduction message. These are displayed at the top of the survey.


Plus the prompt that will ask the participant to take the survey.


Now add some questions


You can choose from three options:

Single selection – participants can choose one of several options.


The participant will the following:


Multiple choice – participants can choose more than one option.


The participant will see something like:


Free form – participants can give textual feedback based on the question.


Mandatory Questions

By checking the “Mandatory” check box it is possible to ensure that participants answer that specific question.

Targeting Groups

If “All participants” is selected then all participant added to your application will be prompted to take the survey.


Alternatively it is possible to narrow down the participants by group (see above)



It’s possible that to add a trigger delay based on current session time (session starts when the participant logs in to the Applause SDK).


In the coming months we will be adding more and more sophisticated triggers.


Finally clicking on ‘Publish Survey’ will open up the survey to your participants!


What can I change after publishing?

It is possible to change anything that might break the logic of the survey.

  • Triggers (currently session time)
  • Targeted groups

You cannot edit question or choice texts. As you might imagine changing the question text in the middle of a survey from “Do you like cats?” to “Do you like dogs?” would invalidate the survey results.

Closing your survey

In the “Publish” tab you can close the survey by clicking on “Close Survey”. Once a survey has been closed no more results will be accepted or presented to participants.

What kinds of data are collected by the Mobile Beta Management platform?

Note:  At no time does Applause collect or store personally identifiable information.  To learn more about  the Applause privacy policies:  Click Here

The Mobile Beta Management platform collects as wide assortment of technical data as well as user feedback. This provides beta managers and their internal teams with a comprehensive view of their beta app and their users’ experience.

Sessions: Offers a real-time view of beta  sessions as they occur. This feature  provides information on app installation, app usage, device type and state, user geo-location, 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.

What is  never collected by the MBM platform includes:

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



I’m attempting to log in to a new beta app for the first time, but I’m being asked for a password?

When you are invited to participate in a mobile beta cycle, you will receive  two emails.

  • The first will be a standard invitation/confirmation request email. You will use the email address the invitation was sent to as your username.
  • The second will contain a unique passcode. This passcode will consist of four numbers. This passcode should be entered as your registration confirmation password.

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 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:


Can I disable or otherwise kill certain builds?

In many cases, you will want to manage your build versions to make sure your beta participants are not using older builds. The Mobile Beta Management platform includes a ‘killswitch’ that can be enabled or disabled for every available build.

When this killswitch is enabled for a build, if a beta participant attempts to launch that build version on their mobile device, the MBM platform will detect the launch, display an alert to the user that the particular build has been disabled, and then prevent the older build from launching.

To enable the killswitch:

Click on the ‘Builds’ tab.

To the right of each versions there’s an options menu. Clicking on “Disable version” will activate the kill switch for that version.

Disabled versions are greyed out.

You can use the options menu to re-enable a version.

How does it work on the mobile side?

Since 3.9.0 we’ve increased the frequency of server side checks.

Android – after each network activity (sending logs, bug, crash or feedback) we perform a check if the build is still active or not and inform the user accordingly.

iOS – since iOS has a much more standardised state model we perform a check when the app is put to the background and brought back to foreground. If the build is no longer active, the user is informed.