What the Server Does, and What It Leaves to the Tablet
What the Server Does, and What It Leaves to the Tablet
The server keeps each child's record, handles sign-in, works out what guides and the school office see and delivers new curriculum content. It does not choose the next exercise and need not be reachable for practice: the tablet carries the curriculum and the engine. The price is that a guide sees answers only once the tablet has sent them.
The server is a program that runs on Fido's side, not on the tablet. It has four jobs.
-
It keeps each child's record: the account, and the
event log of everything the child has done. - It handles sign-in for children and adults.
- It works out what guides and the school office see, from that same record and with the same engine code the tablet runs.
- It delivers new curriculum content to the app.
What the server does not do matters just as much. It does not choose a child's next exercise; the tablet does that itself. And it does not have to be reachable while a child practices. The app carries the curriculum and the engine with it, so even a tablet that has never been online can open its first lesson. When the server has newer content, the app fetches only the parts that changed, and never in the middle of a child's practice.
This division has a price. A guide sees a child's answers only once the tablet has sent them, so a tablet that stays offline all morning leaves that child's row in the guide's view behind.
The record does not lock a school in. An administrator can export a child's record as one file: the account details, every entry of practice, and the notes guides have made.