> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/usability-tests/what-are-usability-tests-in-dscout/device-and-recording-options-in-a-usability-test.md). # Device and recording options in a usability test Usability tests can be run on desktop computers or mobile devices. However, you can only choose one device per mission, and participants must use your selected device type to complete the mission.
You’ll select your device type when creating your mission. We recommend basing your decision off of what experience you’re trying to capture: | Mobile | Desktop | | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | |

Use to test:

|

Use to test:

| {% hint style="info" %} For a comprehensive list of what’s available on each device type, see [Usability testing features by device](/usability-tests/what-are-usability-tests-in-dscout/usability-testing-features-by-device.md). {% endhint %} Each device type offers its own recording options, as described in the sections below. ### Mobile recording options Mobile usability missions are continuously recorded for up to **40 minutes**. After 40 minutes, the participant will no longer be recorded even if they continue to go through and answer questions in your mission.
When you select **Mobile** as your device type, you’ll indicate what you plan to test. Your selection here will determine your mission’s recording type: * **Prototype:** Records only within the Dscout app with the option to record both the participant's screen and front-facing camera. Prototype links are opened directly in the Dscout app so participants can access question prompts and prototypes in a single view. For more information, see [In-app view](#in-app-view). * **Website:** Records only within the Dscout app with the option to record both the participant's screen and front-facing camera. Websites are opened directly in the Dscout app so participants can access question prompts and websites in a single view. For more information, see [In-app view](#in-app-view). {% hint style="info" %} If you’re testing a website that requires participants to access multiple tabs, select **App** instead. This will open any links you provide in the device’s native browser for tab functionality and record the participant’s entire screen. {% endhint %} * **App:** Records the participant’s entire screen. Participants can open any apps installed on their mobile device and the recording will capture what they see. Camera recording is not available. For more information, see [External view](#external-view). {% hint style="info" %} Select **App** if you’re testing something not listed above. For example, if you want to record participants’ use of their device itself, selecting **App** will allow you to record their entire screen, not only what they see inside the Dscout app. {% endhint %} {% hint style="info" %} You can select multiple options from the above list, but selecting **App** will record the participant’s entire screen regardless of any other selections, and you will not have the option to record the participant's camera. {% endhint %} #### In-app view When testing a **prototype** or **website** in a mobile usability test, participant responses are recorded using **in-app view**. This means the recording only captures what’s displayed within the Dscout app. Any links provided will be open directly in the Dscout app so participants can access question prompts and links in a single view. Here’s an idea of how in-app looks to the participant:
#### External view When testing an **App** in a mobile usability test, participant responses are recorded using **external view**. This means the entire screen of the participant’s mobile device is recorded so they can navigate between the Dscout app and any other apps you want them to use during the test. This also allows participants to open websites in their device’s native browser for full tab functionality. External view is required to record outside of the Dscout app, but keep in mind: * Participants must navigate back to the Dscout app to view question prompts. * Prototype and website links will remain in participants’ browsing histories after they complete the mission. * Taps and swipes will not be captured in recordings. * Click data and heatmaps are only captured for Figma prototypes when the Figma integration is enabled. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration.md). Here’s an idea of how external view looks to the participant:
#### Mobile camera recording In mobile usability tests, you can record both the front-facing camera and screen of your participants so long as you're only testing a **prototype** or a **website**. (Testing apps requires screen recording to happen outside of the Dscout app, in which case we are not able to record a participant's camera.)
When testing a **prototype** or a **website**, you'll select from the following options: * **Screen and camera:** Records the participant’s entire screen, front-facing (selfie) camera, and audio for the duration of the test. * **Screen only:** Records only the participant’s screen and audio for the duration of the test (with no camera recording). ### Desktop recording options
When you select **Desktop** as your device type, you’ll choose from the following recording options: * **Screen and camera:** Records the participant’s entire screen, webcam, and audio for the duration of the test. * **Screen only:** Records only the participant’s screen and audio for the duration of the test (with no webcam recording). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.dscout.com/usability-tests/what-are-usability-tests-in-dscout/device-and-recording-options-in-a-usability-test.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.