Your Browser Has Trust Issues: Why Local Devices Break Modern Web Apps
summary
Modern browsers block cloud HTTPS pages from talking to local hardware unless four security gates are satisfied: mixed content (HTTPS→HTTP blocked), CORS permissions, Local Network Access prompts, and explicit USB/user-activation consent. A concrete workaround wraps the web app in Electron so web code talks over an IPC bridge to Node.js, avoiding user-facing prompts; a deployed product, the Proxy Box, puts an HTTPS REST API in front of local devices. Real result: label printing demo goes from minutes per package to seconds and reliably prints in production.
AI-written summary · about
chapters (7)
- 0:00Warehouse to modern web apps
- 7:06Browsers block local devices
- 16:48Four security gates
- 18:35Trust from users to devs
- 20:03Electron for local devices
- 22:16Live demo no warnings
- 23:00Warehouse workers clap
related talks
56mBrowser Invasion: Desktop Apps and the Web
55mWeb Application Security: Browsers Fight Back!
33mA tale of two webs
55mThe Universal Serial Web
59mThe Final Frontier: Security APIs in Modern Browsers
26mEvery Process, Everywhere, All at Once
58mWeb Apps can’t really do *that*, can they?
27mBuilding Cross Platform Desktop Apps With Electron
