Module 0

How to use this

Don't read this front to back. It's a reference, not a novel — roughly the amount of material a semester course would cover, and trying to absorb it in one sitting will just make you feel behind.

Three ways it's meant to be used:

  1. Before you build: read Module 1 and skim Module 2. That's about twenty minutes and it makes the code stop looking alien.
  2. When something confuses you: jump to the relevant module. Every concept in the Spoke codebase has a section here, and Module 11 maps files to concepts directly.
  3. When something breaks: the boxes marked Trap are all real failure modes that cost real developers real hours. They're the most valuable part of this document.

Code samples are complete and runnable in context unless marked otherwise. Where something is genuinely contested or version-dependent, that's noted rather than smoothed over.

Notation

Boxes labelled From Flutter/RN translate a concept you already know. Boxes labelled Trap flag things that will cost you an afternoon. Boxes labelled Why explain design rationale rather than mechanics.

Spoke never sends your voice, your text, or anything else off this Mac. Not a promise in a privacy policy — a property of the binary.