At a Glance
Get feedback on a range of mobile experiences, including web, app, and real-world, by having contributors complete tests on smartphones or tablets. We've compiled a list of frequently asked questions about mobile testing to help you plan your test.
1. How do I set up a mobile test?
You can set up either a recorded test or a Live Conversation session to be completed on a mobile device. When creating the audience for your test, select either Tablet or Smartphone as the device type. You can go further and select the OS in the demographics if you want. Test contributors will only be able to complete your test on a mobile device, and only if they match the demographics you have selected.
2. What are some things I should test on mobile devices?
- Released apps (those found in the App Store and Google Play)
- Unreleased apps
- Web-based experiences
- Mobile prototypes
- Real-world experiences (by engaging the camera on the mobile device)
- AR apps
3. Can I use the device's camera with the Mobile Recorder?
Yes, test contributors can activate both the front-facing and back-facing cameras. If you expect contributors to turn on their camera, it's a best practice to write screeners that share these expectations upfront.
4. What is the recording limit on mobile tests?
We recommend that tests be about 15-minutes long. Technically, the recorders can record up to 60-minutes of video, but you'll need to screen for contributors that have 2GB of free space on their device for a test that long. If you're interested in doing longer tests, please contact your Customer Success Manager.
5. Can I conduct mobile tests with my own contributors?
Yes, you're able to create your mobile test and then use Invite Network to share this test with audiences outside of the UserTesting Contributor Network.
6. How long does it take to receive a completed mobile testing session?
Most Mobile Recorder sessions are completed within hours. Demographics and screening requirements will affect fulfillment time.
7. Do contributors have to be sitting at their computers to complete mobile tests?
No. Mobile tests may be completed anywhere that's safe and legal to use a mobile device (i.e. never while driving). Contributors are not "tethered" to a computer. This means a contributor can freely move about and test anywhere from the park to the couch at home.
8. Do I need to change how I structure test tasks or questions for mobile?
Yes. Avoid written answers when possible. Instead, have people speak them aloud.
Additionally, keep tasks simple, and avoid unnecessary numerous or complex sets of tasks, as contributors may have trouble following them. Contributors will navigate back and forth from the task/question interface and the website or app. As a result, they will not have the task text readily available at all times.
9. What contributor demographics are available for mobile testing?
You'll have the same contributor demographic options as you do with desktop studies.
10. Can I test other companies' apps?
Yes, you can conduct competitor app studies. You'll just need to provide the app's URL for test contributors to download.
11. Do I see any finger input or gestures with a Mobile Recorder test?
On Android tests, you will see where the contributor taps and swipes when interacting with your experience. With iOS tests, you will see these gestures unless the "Native Browser" recording option is selected. In that case, you will see the recording of the screen without these details.
12. What happens when a contributor runs out of space on their phone?
The app will crash and the recording will be lost. Our recorder checks to make sure the user has 400MB free, enough for a 20-minute test. If you're planning a longer recording, screen for contributors who have enough free memory on their device. If this happens to a UserTesting Contributor Network contributor, we'll re-run the test for you with a new contributor.
13. Can I specify that the contributors need to be in a certain location to do a test?
Yes, but you need to keep some things in mind. If you ask for a general location that the contributor would normally be in during the day, they will probably be willing to do that with no special incentive (for example, "take this test outdoors in direct sunlight so we can check how visible the screen is").
However, if you ask the user to make a special trip somewhere in order to take your test (for example, "drive to the grocery store to take this test"), they may not accept the test without proper incentive. For these location-specific tests, you should have a UserTesting subscription with research hours. We'll recruit test contributors willing to go to a specified location and will pay them extra compensation for the time involved.
1. What mobile operating systems and devices are supported?
- All devices running Android 5.0 and later.
- Most Kindles with microphones work (ex: Kindle Fire and Amazon Fire phones, but not e-paper tablets or paper readers).
- All Apple devices running iOS 12 or later.
2. What are the minimum requirements for users to participate in mobile tests?
Test contributors must have iOS 12 (or higher), Android operating system 5.0 (or higher), 400MB of free space when they try to take a test, and at least 20% battery life.
3. Where do I obtain the iOS SDK?
Click here for more information.
4. How is the SDK integrated into my app in the order form?
Upload your iOS app build into the order form, and our order form will take a couple of minutes to attempt to integrate the SDK into your app. You'll know it's successful if you are presented with the option to use the Mobile Recorder. If you do not see that option, you will need to ask your developers to manually integrate the SDK.
5. What does integrating the SDK do?
- Your build will no longer be app store allowable. You should think of these builds as disposable "test" builds. They aren't meant for production, and won't see the light of day outside of a UserTesting test.
- The app can only be opened during a UserTesting test. Opening the app outside a test will show a message saying, "You must be in a test to use this app."
- You or your developers will know you've integrated correctly if you see UserTesting messaging when you run your build in the simulator.
6. How do you deal with landscape (horizontal) vs. portrait (vertical) mobile usage with the Mobile Recorder?
The UserTesting video player interface has a rotate function so you can view both landscape and portrait usage easily.
If the contributor rotates their device during a test, you can use a button on your dashboard to rotate the playback.
7. How is the app distributed to contributors for Mobile Recorder tests?
Upload your build into the order form, as you would to TestFlight or HockeyApp. Your app will be distributed through our system to contributors who pick up the session.
App Testing and Security Questions
1. How do I test unreleased apps?
You can test unreleased apps (i.e. apps not yet available in a public-facing app store) using the following methods:
- iOS: Upload your app (.ipa) file when creating your test. If you upload the file to us, we'll automatically install the app on the contributor's device at the start of the test. NOTE: after it has been uploaded to us and then distributed to contributors, that app file can be used only within the test. (Users won't be able to open the app file outside of the UserTesting test.) Instead of uploading your app, you can also choose to make your app available using TestFlight and then insert your TestFlight link into your draft. We'll ask users to install the app at the start of the test. Users will still have a capability to open the unreleased app after the test has completed (though you would be able to block future users from downloading the file).
- Android: Upload the public beta link or your .apk file during the test creation process. We'll automatically install the app on the contributor's device at the start of the test. UserTesting does not use an SDK for uploaded Android apps, so contributors will still be able to open the app after the test ends. If you do not wish for Android users to access the app after the test, ask contributors to show themselves uninstalling the app in the last task of their test.
2. How do I test released apps?
You can test released apps (i.e. apps that are available for download via the App Store and Google Play) by including the URL to the app when building your test. The test contributor would then toggle between your app to complete tasks and the UserTesting app (where instructions and tasks are displayed), and everything that is displayed on the screen will be recorded along with the contributor's voice in the recording sent to your dashboard.
3. My team has some questions about app security with the iOS SDK. Can you tell me more?
The UserTesting SDK for iOS locks your app to the test. You can't run the test version of the app outside of the UserTesting environment. If someone tries to run your test app outside of a test, an error message will appear and your app will not be accessible. The downloading of the iOS app to the test contributor is also securely facilitated through UserTesting. A user's login is linked to the app download (once they qualify for the requirements of the test).
4. Do I need an SDK for Android testing?
Need more information? Read these related articles.
Want to learn more about this topic? Check out our University courses.