In 2018, Google released some new security features that changed the way you take tests on your Android devices. Due to these security features, you’ll need to enable taps before each Android test. If you don't enable taps before each test, that video won't be useful to our customer, and unfortunately, we won't be able to pay you for it.
Why do I need to enable taps/touches?
On November 1, 2018, Google made some changes to Android security. For UserTesting contributors, the most notable change is how you grant us permission to record where you tap or touch your device's screen. Since our customers can only hear your voice and see your screen, knowing exactly where you're tapping is very beneficial for understanding how you interact with their app or site. Without this data, you won't receive payment for your tests.
How do I enable taps/touches?
When you're ready to begin a mobile test, you'll enter Quick Test Setup.
This will walk you through everything you need to know to start your mobile test, just follow the on-screen instructions.
Open Settings > About Phone > Phone Status. Find the build number and tap it 10 times.
In Developer options, which should now be set to On, scroll down to enable Show taps.
Next, you'll complete a microphone check and a task button tutorial.
Once you've finished uploading your test, you'll want to turn off Developer Options. To do so, go to Settings > Developer Options. Toggle developer options to Off.
Is this a new permission?
No, we've always requested this ability, but the way we do so changed. Previously, you were able to grant this permission once, when installing the app. Now, you'll need to enable it before each test.