Speed, Running It Yourself, and What Is Planned
Speed, Running It Yourself, and What Is Planned
Speed as a commitment on a school tablet, with stated limits and checks; a setup that lets a school run the app and the server on its own machine, built but not yet in use; and what of the app and server runs today, what is planned and what is undecided. Closes with the rest of the series.
Speed is a commitment. On a school tablet, a frozen screen looks the same as a broken one. So the app is held to stated limits. A tap must get a visible response within a tenth of a second. A screen a child opens must show content within a second, not a spinner. Any freeze longer than half a second, even on our own fast computers, goes on a list with someone's name against it. Automatic checks stop the app's start from growing slower without anyone noticing. Not every screen meets these limits yet; the slow ones are on that list.
A school can run it itself. A setup exists that runs the app and the server on one machine a school operates, so that everything stays in the school's hands. Our automatic checks test its configuration. No school uses it yet; today's pilots use the server Fido runs. The public website and the curriculum explorer are not part of it.
What is still to come. A parent's view of their child's progress at school exists only in the demonstration, with sample data. The rule for deleting a closed account's record is undecided.
Two more articles on the software follow: How We Know It Works and How a Small Team Builds Fido's Software with AI.
Questions, objections, or keen to help build it? Write to us.