Skip to content

P1: Add optional Story Notes for first-time Homer readers #14

Description

@Crystal32378

Problem

The current experience can assume more knowledge of The Odyssey than a first-time reader actually has.

A player may encounter names such as the Lotus-Eaters, Cyclops, Circe, Sirens, or Calypso without understanding:

  • who or what they are
  • what is happening in the original story
  • how they relate to Odysseus
  • why the current choice carries a cost

This creates a gap between entering the journey and understanding the stakes.

User evidence

In a first-time / low-context usability test, the player said the story experience had become more interesting, but the mythological names, characters, and relationships were still difficult to follow. The player suggested optional explanations for unfamiliar terms.

This feedback suggests that Odyssey currently works best for readers who already recognize at least some of the story, while readers encountering Homer for the first time need a small amount of optional orientation.

Proposed direction

Add one low-interruption, optional STORY NOTE to each shore.

Each note should explain only:

  1. who or what is present
  2. what is happening at this point in the story
  3. why the current choice matters

Example:

Lotus-Eaters
Their food makes travelers forget home—and lose the desire to return.

Cyclops
Odysseus is trapped by a lawless host. Escape may require secrecy, but pride asks to be known.

Product principles

  • Collapsed and optional by default
  • 1–3 short sentences per shore
  • Human-authored and reviewed
  • No spoilers beyond the current shore
  • No correct answer
  • No trivia or encyclopedia layer
  • Does not affect route logic, Journey Memory, encounters, or ending authority
  • Works on mobile, keyboard navigation, and screen readers
  • Preserves the restrained literary rhythm of the experience

Non-goals

  • Do not redesign the fixed fourteen-shore route
  • Do not add branching navigation
  • Do not turn Odyssey into a textbook or mythology reference site
  • Do not add rushed inline term tooltips before the Build Week submission
  • Do not claim that the current submission fully teaches the complete story to first-time readers

Priority

P1 — post-submission product improvement.

This is an important access-layer improvement, but not a current submission blocker. The next step is not to make the journey shallower; it is to give unfamiliar readers a small light when they need it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions