How do I set up the General tab in Mobile App Testing?

This section covers how to use the General tab to:

• Name your study
• Set the language of your study
• Set up what you want to test
• Choose whether and how respondents must identify themselves
• Protect your study with a password
• Set the ending conditions for the study

Watch how to use General study settings

Localization, respondent identification. restriction of access with a password, automatic closing of your study, and more…

Watch Now

General settings

Name your study, set the study language, and select what you want to test.

Name your study 

• Respondents don’t see the study name displayed anywhere
• Use a name that helps you identify the study on the dashboard

Set the language of your study 

• The selected language determines the labels and headings in the study

Set up what you want to test 

Mobile App Testing supports testing almost anything on a mobile screen. You can select from three main types of media to test:

• iOS native apps
• Android native apps
• Websites
• Prototypes

Any website or prototype is supported, as long as respondents can access it from their device via a link.

After selecting the media type, you will be prompted to insert more information about your app/site/prototype so that it can be displayed to participants during the study.

If you chose iOS native app:

• App name – This is how your app will be referred to during testing.
• URL to App Store or TestFlight – The URL that will allow respondents to download your app at the beginning of the study. You can test an already released app from the App Store, or a beta version from TestFlight.
• App URL scheme – This optional setting allows your UXtweak study to open your app during the testing directly. If you’re not familiar with URL schemes or how to obtain them for your app, you can ignore this setting, ask your developers for help, or read more about URL schemes here. If you don’t include an App URL scheme, UXtweak will open the app’s store page instead. From there, the respondents should be able to open the app.

If you chose Android native app:

• App name – This is how your app will be referred to during testing.
• URL to the Play Store or an APK download – The URL that will allow respondents to download your app at the beginning of the study. You can test an already released app from the Google Play Store, or a beta version via an APK file.
• App URL scheme (Deep Links) – This optional setting allows your UXtweak study to open your app during the testing directly. If you’re not familiar with Deep Links or how to obtain them for your app, you can ignore this setting, ask your developers for help, or read more about Deep Links here. You can also use the package names to select where your respondent will start in your app. If you don’t include an App URL scheme, UXtweak will open the app’s store page instead. From there, the respondents should be able to open the app.

If you chose Website

• Website name – This is how your website will be referred to during testing.
• Website URL – Insert a link that you want to use to open your website during the study.

If you chose Prototype

• Prototype name – This is how your prototype will be referred to during testing.
• Prototype URL – Insert a link that you want to use to open your prototype during the study. In general, this link needs to be publicly accessible so that respondents may open it. For instructions on where to find the public prototype link in major prototyping tools, see the instructions below.

How to retrieve the public sharing link in my prototyping tool?

Figma:

Adobe XD:

Axure RP 9:

Sketch:

Marvel:

Choose whether and how respondents must identify themselves 

Select one of the following respondent identification options:

• Anonymous – The respondents don’t have to identify themselves (default option).
• Email address – Require respondents to provide their email before beginning.
• Other – Ask for another identifier of your choice (e.g. name, screen name, internal company ID).

If the study isn’t anonymous, respondents won’t be allowed to proceed until they identify themselves.

The respondent’s identification will be displayed next to their study results.

If you selected Other identifiers, enabling Allow duplicate identifiers lets multiple respondents use the same identifier (e.g., to identify members of the same group).

By default, your study won’t store respondents’ IP addresses. You can enable this with the Store respondent IP address option.

Protect your study with a password 

There are two ways to protect access to your study link:

• No password – the study is open to anyone with the link
• Private study – requires respondents to enter a password before accessing the study.

The password has to be between 1 and 250 characters long, with no additional demands on the type of characters.

Don’t forget to share the password with the intended respondents!

Set the ending conditions for the study 

Finishing a study ensures that it stops collecting data from respondents. You can finish a study both manually and automatically:

• Manually – End the study anytime you want, without constraints
• Respondent limit – Automatically finish the study once it has reached the required number of respondents.
• Closing date – Automatically finish a study when the deadline has been reached.

Even if a study is set to finish automatically, you can still end it manually at any time by clicking the Finish button.

If the deadline is reached while respondents are still completing the study, they will be allowed to finish.

Other general options

Decide whether and how you want to identify respondents. Decide whether to protect study access with a password. Set rules for automatically ending the study.