> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-trivia-app/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-trivia-app/project-instructions/2-design-and-build-solution.md).

# 2 DESIGN & BUILD SOLUTION

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LDwztHMrXO6GrtroBEo%2F-LEQ9VDkP03dM68IKi17%2F-LEQ9XIMkXyhnM2fRLfC%2FTrivia-Phase-2-Drawing-Alpha-reduced.png?alt=media\&token=f4cc8676-f82b-4bda-9656-bb7d16db472b)

**Design a prototype** of the solution for a detailed internal review and evaluation by a sample of stakeholders. Based on what you learn from your prototype, organize a development strategy to methodically **program and style your solution** with efficiency and quality. Also prepare for the promotion and launch of your solution, and conduct unit testing to ensure all is in working order before an in-class demonstration.

Many of the tasks for this stage may occur in parallel with occasional starts and stops appropriate for your development progress.

| Task                                         | Estimated Time |
| -------------------------------------------- | -------------- |
| Question Bank Development                    | 3 hours        |
| Interface Mockups                            | 2 hours        |
| Interactive Prototype                        | 1 hour         |
| Prototype Evaluation                         | 1 hour         |
| Code Development Outline & Begin Coding      | 6 hours        |
| Marketing Card                               | 1 hour         |
| Code Testing                                 | 2 hours        |
| Prepare Development Review and Demonstration | 2 hours        |


---

# 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-trivia-app/project-instructions/2-design-and-build-solution.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.