The Device Most Students Actually Have
School fleets standardised on Chromebooks because they are cheap, centrally managed and hard to break. The same management that makes them practical also means a student cannot install anything, and usually cannot approve an extension either.
Any tool that needs installing is therefore not available to the people who most need it.
What Gets Blocked
Installs, extensions, and often whole categories of domains. Policies vary by district, but the pattern is consistent: the browser works, and very little else is negotiable.
Why Client-Side Matters Here
A page that does its work in JavaScript on the device needs nothing but the page itself. No account, no server round trip for each calculation, no data leaving the machine. That last point is what lets a tool be used without a data-processing agreement, because there is no data to process.
Offline and Flaky Connections
Once a client-side page has loaded, it keeps working if the connection drops, because nothing further is being fetched. On school wifi at 9am that is a real advantage over anything that queries a server per keystroke.
What to Look For
A tool worth using on a managed device loads in one request, works without signing in, and does not ask for permissions it has no use for. If a calculator wants an account, the account is the product.
