Introducing Screen Recording (since 3.x.x)

Versions  3.x.x of both our Android and iOS SDKs support screen recording to enable users to record their screen while recreating a bug or crash.

  Supported OS’s

iOS Android
Post 6.0 Post 5.x (Lollipop)


Shake your device to pull up the Bug vs Feedback UI



You’ll notice now in the attachments there’s a new option:

Tap on ‘Add App Screen Recording

Then you will be returned to the app and your screen is being recorded.

The recording will end either when you shake the device again or after 1 minute when you will be returned to the problem report screen


You can tap on the Screen Recording to preview it.




From the Bug report UI tap on “ADD NEW  –  and then tap “TAKE  VIDEO” you’ll see a system notification alert so tap “START NOW

You will be returned to the app and there your screen is recorded until either the 1 min timer expires or you can end it via the notification centre.


You’ll see the video as an attachment and you can also play a preview within the SDK.


Question iOS Android
Max. length of a screen recording video? 1 min. 1 min.
Video Quality   Depends on device 1500 kbps
Video Format Details   Mpeg4 /  H264 Mpeg4 /  H264
Videos  storage location   Application’s sandbox Application’s sandbox
When are videos removed? When  app is removed, and once video is posted to server When  app is removed, and once video is posted to server


Ensure Testers are getting the most out of your app and the SDK

We have just launched two new improvements that will improve  QA process by

  • Informing users what’s new for a specific build with an in-app splash screen
  • Showing a tutorial upon first launch of a new build (and alongside any splash screen)


In-app splash screen:


In the Builds page click on the build you wish to add a splash page.

In the next page add your Splash Message (for in-app) you can choose to add basic formatting like bold, italic and paragraph formatting with hyperlinks.

When the app is started up here’s what the user will see (iOS)

Alongside this there’s also an in-app SDK Tutorial

In-app SDK Tutorial

The in-app SDK tutorial will be shown in the following conditions:

  • First run of a new build
  • Alongside a new splash screen (see the previous section)

The tutorial is a simple guide to using the Applause SDK


Disabling the in-app SDK Tutorial

The tutorial can be disabled via the settings page of your application in the web panel.


Latest versions of the Applause  SDKs can be found at:-

New testing possibilities by adding images from Gallery/Camera to Bug Reports!

Since version 2.9.1 of the Android SDK and 2.3.0 of the iOS SDK it is now possible to attach external images to your bug reports.

This opens up the Applause SDK to testing anything from smart watches to self driving cars. So if you’re testing hardware or need to add a screenshot you took outside the Applause SDK it’s now possible.

Expect the UI to be updated 🙂 but we wanted to get this feature into your hands as soon as possible.

Android SDK:

screenshots_png   Screenshot_2015-06-09-17-02-08



IMG_0100    IMG_0103


Android New Permission Required:

To enable the new features please add the following permission to your application manifest.xml

<uses-permission android:name=”android.permission.READ_EXTERNAL_STORAGE” />

iOS Permission:

The SDK will trigger the OS permission request to access the users Photo Library at the first attempt to add an image from there.

Is there a quick way to start in-app testing (without being anonymous)?

The default method to log in to start in-app testing is your email address and password.

Typing on mobile devices is always a pain, especially if you have a long and secure password.

There are some cases where having a quicker authentication method is required to reduce friction and encourage participation from your user base.

In your app the log in screen will change from the default:

to the rather snazzier:


The user can pick their name / avatar (taken from

How to make the switch to quick authentication

Go to your app’s settings and ‘Login Method

Choose Quick Authentication


We recommend only changing this method before distributing a new build rather than mid QA.

Known Issue:

Please note that if you have users already running apps with the mobile sdk and you change login  method from they will have to restart their mobile apps.  

There may be some unexpected behaviour in apps with open sdk sessions if the login method is changed. However, restarting the app will solve any such issues.