> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/code-chatbot-1/warm-up-project-outline/2-read-and-discuss.md).

# 2 Read and Discuss

## Objective

Read about design aspects of conversational interactions with bots and synthesize your understanding in writing and discussion.

### Video: "Actions on Google: Conversation Design Tips"

{% embed url="<https://www.youtube.com/watch?v=MSUPVbbhIGA>" %}

## Instructions

1. Read [**Why Bots are the next Big Bang in UX** *by Sophie Riwaters*](https://chatbotslife.com/why-bots-are-the-next-big-bang-in-ux-643b2e66a2a0)
   * What advantages/disadvantages do bots have over mobile apps?
   * What do you think the best uses of bots are or will be?
2. Read [**How can you create a simple working Chatbot in 2 hours from scratch** *by Sophie Riwaters*](https://blog.prototypr.io/how-can-you-create-a-simple-working-chatbot-in-2-hours-from-scratch-f92c31c7e974)
   * How does the process of designing an app compare to the process of designing a bot?
3. Read [**A Guide to Developing Bot Personalities** *by Jess Thoms*](https://marvelapp.com/blog/guide-developing-bot-personalities/)
   * Why is a bot personality important?
   * What factors influence the design of a bot personality?

## ✓ Deliverable

Document your answers to the questions above for each reading and be prepared to discuss in class.


---

# 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://docs.launchboard.app/cxd/code-chatbot-1/warm-up-project-outline/2-read-and-discuss.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.