Blazor internal tools: when WASM is not the first answer

Internal tools often ship under staffing constraints. We teach a simple matrix: latency sensitivity, offline needs, operational tolerance for circuit churn, and whether your security team already blesses WebSockets.

We walk through a warehouse scanner dashboard that stayed on Blazor Server because operators valued instant updates over offline mode. The opposite case—a field tablet with flaky Wi-Fi—nudged a WASM prototype.

We also cover bilingual label loading because mixed teams notice awkward fallbacks faster than engineers expect.

We finish with a candid limitation: we do not promise pixel-perfect parity with mature React ecosystems; we promise clarity on trade-offs.