Mobile Tests: Best Practices

At a Glance

Just as mobile apps are different from desktop apps, the process of running a usability study on a mobile device is different from recording one on a desktop computer. Here are some guidelines from our team.

 

General

  • Our iOS browser doesn’t yet support tabbed browsing. If you're running a comparison test or a competitor web test on iOS, you’ll need to specify the links for each site in the test plan when you want contributors to see them. For example, if you’d like contributors to look at site A and B in quick succession, you should write out both URLs in the task so that contributors can access them correctly.
  • When testing apps on iOS devices an SDK will need to be incorporated into a testing version of your app. This does not apply to app tests taken on Android devices.
  • Native Browser. Use this option when you require advanced browser functionality (like multiple tabs), or you've noticed issues with your prototype loading on our browser. Contributors will use Safari or Chrome, depending on their operating system. Note that selecting this option will change the recording method in such a way that finger-taps will no longer be captured. 

NOTE: Keep in mind that if you're using the in-app browser and something doesn't quite look right in the videos you're receiving, we ask that you recreate the test using a native browser.

Test Length and Tasks

  • With iOS tests, reiterate the site/app you are testing in the first task. Doing so will help contributors understand what they are testing, and what they should be looking at before proceeding through tasks.
  • Android tests automatically display the start URL as the first task, so repeating it is not necessary.
  • Keep tests as close to 15 minutes as possible. Contributors expect tests to take no longer than that. Test sessions longer than 15 minutes may cause contributor fatigue, which often diminishes the quality of the feedback. Keep in mind that test sessions on mobile devices tend to be shorter than those on desktop.
  • Keep task descriptions short. There is a limited amount of space to display the task description on screen, so concisely written tasks are best. Also, push the most important details toward the front of the task.
  • If asking for feedback on a specific page, provide the URL. Providing the URL will help contributors quickly get to the page you’d like feedback on, and allow them to return to that page should they navigate elsewhere.
  • Use shortened URLs. To conserve space, use condensed URLs (created through a service such as bit.ly) when including links in task descriptions. Long links can crowd up the screen!
  • Five-second test: Due to inconsistent loading speeds for mobile connections, avoid using the five-second test when using the Mobile Recorder.

Questions and Ratings

  • Avoid too many written-response questions. Typing on a mobile device can be cumbersome, and can lead to contributor fatigue during the study. Use written-response questions sparingly, opting for verbal responses instead.
  • Direct contributors to write their answers to written-response questions in the “box below.” Some contributors begin answering the written-response questions verbally, so the entire response may not be captured in writing. Reminding them to type their answers in the provided box will help capture the full written response.
  • Multiple choice and rating scales are great for mobile tests. Try to incorporate these types of questions (if available) in your study, because they don’t require lots of typing.

Learn More

Need more information? Read these related articles.

Want to learn more about this topic? Check out our University courses.

Was this article helpful?
7 out of 15 found this helpful