> 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.7-product-video.md).

# 2.7 Product Video

{% tabs %}
{% tab title="✓ TASK" %}
Your team will create a **product demo video** that will briefly demonstrate and explain your working smart device prototype and its web app. You'll include the video in your team's [product marketing website](/project-internet-of-things/project-instructions/2-design-and-build-solution/2.6-product-website.md).

1. Create a script and [narrative storyboard](https://docs.idew.org/principles-and-practices/practices/design-practices/narrative-storyboards) for your team's product demo video, which should be about 1-2 minutes in length. As necessary, tailor the video content to your target users, as represented by your team's persona. Be sure the video will be clear, concise, engaging, and professional.
   * For the script, be sure you'll show and explain what the smart device and web app do, as well as the value they provide to users.
   * For the storyboard, decide which [types of camera shots](https://docs.idew.org/principles-and-practices/practices/design-practices/narrative-storyboards#types-of-camera-shots) will be most effective for the different parts or scenes in the video. When necessary, be sure to capture close-up shots of the smart device or web app to show important details.
2. Use your script and storyboard to practice the video.
   * The person(s) that will act and/or narrate should practice what they will do and/or say.
   * The camera person should practice capturing the camera shots using different camera movements (tilting up or down, panning left or right, zooming in or out, etc.).
   * If your team can record the final video (and its audio) in one continuous take, you'll avoid or minimize the need to edit the video.
3. Record and finalize the video.
   * If necessary, record additional takes.
   * If necessary, edit the video to finalize it (cut and splice scenes, add titles or captions, add narration or background music, etc.).
   * Upload the final video to a site (such as: Google Drive, YouTube, etc.) that will allow you to embed (or link to) the video in your team’s product marketing website.

### **❏ Deliverable**

Submit a link to your team's product demo video for its smart device solution.
{% endtab %}

{% tab title="➤ EXAMPLE" %}
Here's a real-life example of a product video:  [Fitbit Charge 3 fitness tracker](https://www.youtube.com/watch?v=omJhc4iv4z4)

Because your team's device is a first version prototype, your video will be more of a demonstration, rather than a polished commercial for a finished product.
{% 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.7-product-video.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.