The application is fully browser-based, so it runs on managed Chromebooks exactly as it does on Windows. There is nothing to install and no Chrome extension to approve. Districts commonly pin it as a web app through the Google Admin console so it opens in its own window.
Every workflow is available on a Chromebook. The one hardware-dependent feature is NFC tap-to-identify, which requires an Android device with Web NFC. Every place NFC appears also offers a manual student picker, so no task is blocked on a Chromebook.
The rugged Android handhelds used for NFC are managed Android devices. They can be enrolled, locked down, and updated through the same UEM/MDM console the district already uses for Chromebooks (Google Admin, Microsoft Intune, VMware Workspace ONE, and similar). That keeps the handheld fleet under the same policies, app allowlists, and remote-wipe controls as the rest of the district's devices.
Student-facing surfaces are Chromebook-first by design. The student statement kiosk used during a discipline investigation and the read-only family view both work in a standard browser tab with no camera, no NFC, and no special permissions. The kiosk locks to a single student's statement and clears itself on submit.