> 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/product-updates/2024/april-2024.md).

# April 2024

## What's new?

### FIELD

#### Express

* **Run mobile usability tests**\
  You can now run [mobile usability tests](https://help.dscout.com/hc/en-us/articles/360040417412) on your prototypes and app experiences on dscout! You'll get up to 10 task questions, with 10 minutes of recording for each, as well as photo questions, usability metrics, heat maps, and more.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/yLvXdouYNwJRxPRvBkpb/25463578722708)
* **Introducing task success validation**\
  We've added automated [task success validation](https://help.dscout.com/hc/en-us/articles/18520466351636) for those who want an extra level of verification in addition to measuring task success based on self-reporting. You can now set a success web URL on desktop or a success screen in your Figma prototypes on desktop or mobile.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/9jKKndRDbe1I4Yhr56Qd/25463586613140)
* **Updated Figma capabilities**\
  Add your Figma links a level higher on the study or mission itself rather than at the individual question level, and dscout will [collect heat maps](https://help.dscout.com/hc/en-us/articles/18520617213332) for the entire file. With task questions, you can select a starting frame where the participant is directed at the start of each task. Also, you can now [manage all Figma URLs](https://help.dscout.com/hc/en-us/articles/18519357739412) in a mission-level modal, meaning you can see and edit the URLs or prototypes you've added to each task. You can also see which task questions are used in the mission and easily add, remove, or refresh any connected prototypes or URLs from one central place.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/DRyLX1vy9PBnpnGpUxZG/25463586616596)
* **Try test mode in Express missions**\
  Have you ever wanted to test a mission you're setting up before it goes to scouts? With our [new test mode](https://help.dscout.com/hc/en-us/articles/25306920154644), you can now send media surveys or usability tests to up to 5 teammates for internal testing and see test data in the analysis views.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/Yje1hMRDcUFwB9V0ixsq/25463578726676)


---

# 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/product-updates/2024/april-2024.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.