Ritesh FirodiyaWork / Tic Tac Toe / Wiki
Tic Tac Toe wiki
What a picture cannot hold: the rules that only break across screens, the product’s own names and numbers, and why each screen is drawn the way it is.
13 pages · last verified 2026-09-22
Concepts 2
| Page | Owns |
|---|---|
| hard-is-unbeatable | Hard is perfect minimax, and the app must say so |
| reserved-colour | Blue is X, rose is O, amber is the winning line — and nothing else may be |
Entities 1
| Page | Owns |
|---|---|
| monetisation | Ads are the whole model. No IAP, no subscription. |
Surfaces 8
| Page | Screen |
|---|---|
| board-loading | game/board-loading.html — the computer thinking |
| board | game/board.html |
| draw | game/draw.html |
| how-to-play | settings/how-to-play.html |
| lost | game/lost.html |
| splash | The launch screen, before the first route renders. |
| start | home/start.html |
| win | game/win.html — the game-over sheet |
Decisions 2
| Page | Decided |
|---|---|
| 2026-09-19-designs-backfilled-after-shipping | The wireframes for this app were drawn from the shipped source, after release — and from 2026-09-19 onward the wireframe is nonetheless the spec. |
| 2026-09-22-design-peripherals-standardised | This set adopts the estate-wide design peripherals: one surface folder per surface, the six-section gallery, the generated breadcrumb and surface switcher, the closed variant vo… |