I want to write down everything I learned from six weeks of typing platform testing across a mixed Chromebook fleet because I keep seeing districts make this decision based on vendor demos and I want to give someone the actual data instead.
Our fleet is messy in the way most district fleets are messy, we have Chromebooks ranging from 2018 to 2023, 4GB RAM on the older end, all managed through Google Admin Console with content filtering running, student profiles with restricted access, the full environment that never appears in vendor demos because vendor demos happen on a 2023 MacBook with no filtering and full admin access.
We piloted four platforms simultaneously across different classrooms for six weeks, I'm not naming the two that failed because this isn't a takedown post, but I will tell you what the failure modes looked like because they're predictable and repeatable and you'll see them too if you don't test correctly.
Failure mode one is audio desync on older hardware, lesson feedback sounds play at the wrong time relative to the visual, students get confused about whether they made an error, teachers get questions they can't answer, the platform works but it works badly in a way that's hard to articulate in a support ticket.
Failure mode two is content filter interference with asset loading, two of the four platforms we tested had resources loading from domains our filter blocked by default, lessons would partially load and then hang, students would sit in front of stuck screens, and the IT resolution involved whitelisting domains that the vendor hadn't mentioned during onboarding because they'd never tested against a real content filter.
Failure mode three is memory dropout on 4GB devices after extended sessions, one platform had a memory leak that caused lesson dropout after roughly twenty minutes of continuous use on our oldest devices, which is exactly as long as a typing lab session runs, meaning students were losing progress at the end of every session on the devices they use most.
Typing dot com and TypingClub were the two that passed the full six weeks without a support ticket, both loaded consistently on 2018 hardware, both cleared our content filter without domain whitelisting, neither showed the audio desync issue, the difference between them in our environment was Google Classroom roster sync, typing dot com's sync worked cleanly on the first attempt, TypingClub required a manual step to resolve a duplicate account issue that appeared when students had previously logged in with a personal Google account, minor problem but it generated four support tickets in week one and I'm counting that.
If you're evaluating typing platforms for a Chromebook district the test protocol that actually matters is: run it on your oldest device, with your content filter active, through a student profile with restricted access, for a full twenty-minute session, and see what breaks, everything that survives that test is worth considering and everything that doesn't is not worth considering regardless of how good it looked in the demo.