The response data that we send to Firebase should include how long it took the user to respond.

Questions

1. How to define the "start" of the response time period? From the time the page is visible?

This issue includes:

• Creating a sticker board
• Creating some sort of sticker assets
• Creating an animation to show that the sticker is awarded
• Saving the sticker to the sticker board

Questions

1. Where should the sticker board live?
2. How much of a notion of a "user" do we have? Is it okay if the sticker board is only local to their own device?

This is already supported in the content model.

• Show the cover on book selection
• Show the cover of the book as the "page" of the book

Update Please see my next comment that outlines a better approach for dealing with this.

For normal book reading, we decide if we are using a number or size prompt based on the "mode" (which is in turn based on the "treatment" that is set up at the beginning).

However, for pre- and post-tests there is only one prompt and correct answer per question.

So when choosing a prompt and when grading answers, the logic will need to be updated by passing in the "type" (pre-test, post-test, or regular book) so that we can update the logic.

Effected places:

• Getting the choices
  Currently, this based on difficulty. However, for pre- and post-tests, difficulty is not relevant. So we need to detect that we are in a pre- or post-test and simply select the one difficulty level that is present.
  src/models/Question.ts#getDifficulty
• Getting the prompt: src/models/Question.ts getPrompt
• Grading a selection
  src/models/Question.ts#isSelectionCorrect which in turn depends on src/models/Choice.ts#isSelectionCorrect.
  For a regular book, identifying the correct answer depends on the mode. However, for pre- and post-tests, we will make the assumption that only one of the fields is specified - either the correct number stimulus or the correct size stimulus. So we will need to pass along information about the book type. If a regular book, use mode as normal. If a pre- or post-test, then ignore the mode and identify which field is not null and use that one.

To identify more places that may be effected, in VS Code do a global search for "mode" - CTRL + SHIFT + F to open up the global search on windows.

We need to identify what fields she would like to be able to filter on and gather any other requirements she has for reporting.

Especially useful for children during "play at home" sessions. They can ask the book to read the page out loud to them.

Questions

1. Should the option be selected at the beginning and last for the entire session?
2. Or should each page have an "audio" symbol that can be touched to prompt the page to be read?

• Update existing metabase queries to extract this new field and fall back to "regular" as a default when the field is not present.

I think this is probably the most complicated feature in the backlog because of the hidden complexity. This will likely need broken apart into more issues:

• Render named characters to the screen. The child should press on the character to select a stimulus rather than clicking on the stimulus itself.
• Make a character selection screen at the beginning of the book. The child should be able to choose two characters to represent the left and right stimuli.
• Perform text substitution on the page text. Maybe have a format where in the CMS you can use [[left]] and [[right]] and we will replace these pieces of text with the name of the character.

If a background image is configured for the book, it should display behind every page and question, full-screen if possible.