Skip to content

Screens ​

Status: planned specification. This page describes the target product; some elements already exist. See the current implementation inventory for shipped routes, architecture and known gaps. Do not treat this specification as evidence that all described behavior is implemented.

This document indexes route screens, route experiences, and Play flow screens.

Detailed definitions live in dedicated docs under ./06-screens-catalog/.

Purpose ​

This page does two jobs:

  • index dedicated screen and experience docs
  • keep only short shared notes that span more than one dedicated doc

Screen index ​

ScreenKindRoute or entryDetail doc
Explore entryRoute screen/{locale}/exploreExplore Entry Screen
BrowseRoute screen/{locale}/explore/alphabet, /{locale}/explore/vocabularyBrowse Screen
StudyRoute screenStudy lesson and module review routesStudy Screen
PlayRoute experiencePlay lesson and module review routesPlay Experience
Play LobbyFlow screenPlay route initial statePlay Lobby Screen
Play RoundFlow screenActive round statePlay Round Screen
Play ResultsFlow screenEnd-of-game outcome statePlay Results Screen
Play Mistakes ReviewFlow screenPost-results review statePlay Mistakes Review Screen
TranslitRoute screen/{locale}/translitTranslit Screen
SettingsRoute screen/{locale}/settingsSettings Screen
Recovery screensRoute statesGlobal not found and resource unavailable statesRecovery Screens

Shared Screen Patterns ​

Browse pattern ​

  • Used by the Browse routes
  • Shared role: browse one content family, select one study resource, and launch Study or Play
  • Shared rules:
    • every browse route exposes exactly one Full review section
    • Full review is the UI label; the underlying product model is a module review set
    • browse cards use the same shared grid structure across content families
    • only the preview visual asset changes by content family
    • the selected study-resource surface is contextual, dismissible, and non-modal
    • selecting another resource updates the same surface in place

Study pattern ​

  • Used by the lesson and module review Study routes
  • Shared role: review one route-provided item set before Play
  • Shared rules:
    • the route provides title, content family, item set, and back target
    • the study navigation bar is shared across content families
    • summary shows all items and is scrollable
    • detail shows one item at a time
    • Play remains available in summary and detail

Play pattern ​

  • Used by the canonical Play routes for lessons and module review sets
  • Shared role: generate a game for one route-provided set and run the full Play flow
  • Flow order:
  • Shared rules:
    • Play generates the game before the Lobby is shown
    • one active round is shown at a time
    • answer buttons submit immediately
    • the first wrong answer marks the round failed and enters corrective elimination inside the round
    • the round includes active, corrective, and resolved states inside the same screen
    • resolved rounds pause briefly and then auto-advance
    • Results show the outcome first, and the failed-result variant includes entry into Mistakes review
    • leaving from an active or resolved round state uses a confirmation surface because progress would be lost

Recovery-state pattern ​

  • Used by Recovery Screens
  • Shared role: help the student recover from invalid URLs or valid routes that cannot load their required resource
  • Shared rules:
    • valid controlled routes with missing data use route-owned unavailable screens instead of collapsing into global not found
    • the safe return destination is /{locale}/explore
    • route-owned unavailable states are separate from the normal Study and Play experiences

Dedicated Screen Docs ​

Route screens and experiences ​

Play flow screens ​

Recovery route states ​

  • Recovery Screens: grouped contract for global not found, Study resource unavailable, and Play resource unavailable