Screens are files

Five screens, five JSON files, one host that never learns what any of them contain.

Intro5 lessons25 min
  1. 1The Screen Is a File — Starting a UI Runtime in Four LinesScreen course, part 1. What exactly was that blob the server sent in client part 4. It starts with one four-line JSON file and one host that never looks inside it.5 min
  2. 2A Direction and a Gap — Layout Without CoordinatesScreen course, part 2. Placing several things looks like it needs coordinates, but linear takes only a direction and a gap. Why avoiding coordinates is a condition here, not a taste.5 min
  3. 3The Number Is Not in the File — One File, Two PicturesScreen course, part 3. One `{{now}}` splits the screen from the value. Whether it really split is settled by rendering the same file twice under two different states.5 min
  4. 4A Button Names a Tool and Stops ThereScreen course, part 4. There is no code in onTap, only a tool name. Whether that name actually reached the host cannot be seen in a picture, so the harness presses the buttons and writes down what arrived.5 min
  5. 5One File, Two Shapes — A List That Does Not Know Its LengthScreen course, final part. conditional splits the screen, list builds rows without knowing how many, and sixteen pieces across three tracks meet.5 min