> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-internet-of-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/project-internet-of-things/project-instructions/2-design-and-build-solution/2.4-prototype-evaluation.md).

# 2.4 Prototype Evaluation

{% tabs %}
{% tab title="✓ TASK" %}
Your team will **test the interactive prototype of your web app** with people outside your team to evaluate whether the web app's design is easy to understand and use. Receiving constructive feedback will allow you to make improvements in the design before coding the web app.

[Follow these instructions to conduct user testing](https://docs.idew.org/principles-and-practices/practices/design-practices/user-testing) of your team's interactive prototype. User testing consists of four major steps:

1. Create Task Scenarios
2. Recruit Participants
3. Facilitate Testing Sessions
4. Summarize Findings

[Use this template](https://drive.google.com/open?id=1lQUSyjqKTbo1Pth34okLd43AZw2O_zkC7zYE1grwHv0) to summarize your team's evaluation findings.

Based on the evaluation findings, make any necessary changes in the design of your web app before your team starts coding it. Create new sketches or mockups to show the revised interface design for the web app prototype.

**IMPORTANT:**  Be sure to keep a copy of your **original** interactive prototype.

### **❏ Deliverable**

Submit your team's evaluation findings & revised web app design
{% endtab %}

{% tab title="➤ EXAMPLE" %}

{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard** | **✓ Meets Standard** | **✓+ Exceeds Standard** |
| --------------------- | -------------------- | ----------------------- |
| Description           | Description          | Description             |
| {% endtab %}          |                      |                         |
| {% endtabs %}         |                      |                         |


---

# 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://docs.idew.org/project-internet-of-things/project-instructions/2-design-and-build-solution/2.4-prototype-evaluation.md?ask=<question>&goal=<endgoal>
```

`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.