The Parts and How an Answer Travels

The Parts and How an Answer Travels

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

The parts of the software - the curriculum as data, one shared engine, the app, the server, the explorer and the website - and the path of one answer: drawn by the shared engine inside the app, stored on the tablet, synced to the server, where the same engine code computes the guide's view. Prepares the later articles on the curriculum, the engine and the app and server.

The software has a handful of parts, kept together in one code base.

  • The curriculum holds every topic, exercise, and article as plain data files, not as screens. The other parts read it.
  • The shared engine is one library that displays exercises and articles and contains the mastery engine. It does not run on its own; the other parts build it in.
  • The app serves children, guides, parents, and the school office. It runs on Android tablets and in the browser.
  • The server keeps the records, handles sign-in, and works out what each guide sees.
  • The explorer is a public website on which anyone can read the whole curriculum, this article included.
  • The website introduces the school.

How the parts fit together shows in the path of a single answer.

Where does one answer go after a child taps it? Step through with +.

A child taps an answer. The exercise comes from the curriculum and is drawn by the shared engine inside the app. The app writes the answer into the tablet's own storage, as an entry in the event log, and sends it to the server once there is a connection. On the tablet, the mastery engine works out what comes next. On the server, code from the same engine works out, from the same entries, what the guide sees. Tablet and server read one record.

Three later articles take these parts further: Curriculum as Data, Rendered Anywhere, The Mastery Engine, and The App, the Server, and Where a Child's Work Lives.

Keine Aufgaben fĂĽr dieses Thema.