One Piece, Shown Everywhere
One Piece, Shown Everywhere
How the shared engine turns the files into pages in the app on the tablet and on the public explorer, so a correction made once appears in both; interactive figures as reusable building blocks; what is prepared in advance (formulas, offline articles) and what the build refuses to ship. Prepares the curriculum tree.
The files are not yet pages. What turns them into pages is the shared engine named in The Shape of Fido's Software: one library of code that knows how to draw an article, an exercise, a worked example, or a reader text, and how to check an answer.
The same library runs in two places today. In the app, it draws every article, exercise, and reader text a child sees on the tablet. On the public explorer, it draws the same pieces for anyone with a browser. A correction made once therefore appears in both. The app itself holds no lesson of its own. It decides which piece to open next and keeps the record of what the child did.
Interactive figures are reusable building blocks: a graph whose point a reader drags, or a clock that converts between 12-hour and 24-hour time. The library holds about ninety building blocks, most of them figures like these. An author places one in an explanation with a single line and sets it up with a few settings. So a new article needs writing, not programming, unless it calls for a building block that does not exist yet.
Some work is done in advance, when the curriculum is built. Formulas are typeset then, so they appear at once. Articles for the tablet are prepared then too and travel with the app, so they open without a connection. A new article needs no new app code, but it reaches the tablet with the next update of the app.
The build also refuses to finish when a page would come out wrong: when an explanation file is missing, or when a highlighted term has no color assigned.