> 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/recruit-participants/working-with-participants/participant-technology-requirements.md).

# Participant technology requirements

For participants to succeed in Dscout studies (and for you to collect the best data), it's important participants have the right equipment. What they'll need depends on the study type as well as the type of device you're conducting that study on. Use the sections below to understand what your study's specifications will mean for your participants' technology requirements.

### Screeners

| Screener type                                                                        | Mobile app   | Web extension | Web browser                                                                                                                                                                            |
| ------------------------------------------------------------------------------------ | ------------ | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Public screeners** (auto-recruiting from the Dscout Scout Panel or Partner Panels) | ✅ (Required) |               | <p>Scouts in the Dscout panel discover new screener opportunities through the Dscout app.<br><br>Scouts can complete web-based screeners if sent a screener webpage link directly.</p> |
| **Private screeners** (inviting your own participants)                               |              |               | ✅ (Required)                                                                                                                                                                           |

### Diary studies

{% hint style="info" %}
**Note:** Desktop diary activities **don't require the Dscout browser extension**. Participants complete them in Chrome or Edge, and they're never prompted to install anything.
{% endhint %}

| Device type                                             | Mobile app   | Web extension | Web browser                        |
| ------------------------------------------------------- | ------------ | ------------- | ---------------------------------- |
| Diary study with **desktop** activities                 |              |               | ✅ (Google Chrome or Edge required) |
| Diary study with **mobile** activities                  | ✅ (Required) |               |                                    |
| Diary study with both **desktop and mobile** activities | ✅ (Required) |               | ✅ (Google Chrome or Edge required) |

### Interview studies

| Device type | Mobile app   | Web extension | Web browser                        |
| ----------- | ------------ | ------------- | ---------------------------------- |
| **Desktop** |              |               | ✅ (Google Chrome or Edge required) |
| **Mobile**  | ✅ (Required) |               |                                    |

### Usability tests

| Device type                | Mobile app   | Web extension  | Web browser                        |
| -------------------------- | ------------ | -------------- | ---------------------------------- |
| **Desktop** usability test |              | ✅ (Required)\* | ✅ (Google Chrome or Edge required) |
| **Mobile** usability test  | ✅ (Required) |                |                                    |

{% hint style="info" %}
**Note:** You can bypass the need for participants to have the Dscout browser extension in desktop usability tests; however, less data will be collected. For more information, see [Manage participant experience in a usability test](/usability-tests/create-a-usability-test/manage-participant-experience-in-a-usability-test.md).
{% endhint %}

### Media surveys

| Device type              | Mobile app   | Web extension | Web browser  |
| ------------------------ | ------------ | ------------- | ------------ |
| **Desktop** media survey |              |               | ✅ (Required) |
| **Mobile** media survey  | ✅ (Required) |               |              |

### Intercept studies

Intercept studies are desktop-only and always require the Dscout Chrome extension.

### AI moderated studies

AI moderated studies are desktop-only and the Dscout Chrome extension can be required or not per your choosing. For more information, see [Manage participant experience in an AI moderated study](/ai-moderated-studies/create-an-ai-moderated-study/manage-participant-experience-in-an-ai-moderated-study.md).

For more information on device requirements, see [Minimum device requirements](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196-Minimum-device-requirements).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/recruit-participants/working-with-participants/participant-technology-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.