The Screens, the Curriculum, and the Clock

The Screens, the Curriculum, and the Clock

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

Automated walks through the app's screens as a child, parent, guide, teacher or administrator would take them, on demonstration data; machine checks on every curriculum change and human review before content reaches children; and speed limits, each a checked-in number, timed on a slowed computer that stands in for the tablet.

Walking the screens. The fourth layer uses the app as its users do. A tool drives the app in a browser, finds every screen it can reach and every control it can press, and records them as a map. Paths through that map are walked automatically, as a child, a parent, a guide, a teacher, or an administrator would walk them. As of November 2026 there are 1,534 paths: 34 written by hand, each naming the person it serves and what they want to do, and 1,500 generated to cover the steps the map records. The walks run on demonstration data in a test copy of the app, never on children's records.

Checking the curriculum. The curriculum is data, and machines check it on every change: every link must lead somewhere, nothing may be left unreachable, and every page must build before it ships. People check it too. Review marks and release stages decide which content children see, as Curriculum as Data, Rendered Anywhere explains.

Timing it. A school tablet is slow, and a frozen screen looks broken to a child. So the software has speed limits, each written down as a number. No single stretch of work may hold up the screen for more than half a second without becoming a tracked problem. The code the app loads at the start must stay under a fixed size. Opening the app and answering a card must each stay within a measured time. These times are taken in a browser on a computer slowed to a quarter of its speed, standing in for the tablet. A limit is raised only by a reviewed change that states the new measurement.

Keine Aufgaben fĂĽr dieses Thema.