Feature Library

LAN phone remote

<0.01 CPU ms
A still of the LAN phone remote demo
Still
The live demo starts when it’s in view.Scan the code on the phone, type the code, press Next · or try a wrong code, freeze the presenter, reset · nothing leaves your browser

A phone on the same Wi-Fi steps a presentation, with no cloud and no app: scan a QR code, type a six-digit code, and Next and Back go to the presenting machine.

What it costs a frame

<0.01 ms
GPU
not used
CPU, median
<0.01 ms
CPU, 95th pct
<0.01 ms
Draw calls
0
Weight
Light

Measured 11 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured with the phone paired and pressing Next and Back about three times a second over the in-page network (no delay), the presenter publishing four times a second and applying each command, and the hub panel redrawn on each change. The slide’s sun and sky transitions run in CSS. At rest the two polling loops (the protocol itself) still run: a publish every 250 ms and a state read every 350 ms. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed<0.01<0.01
apple · Apple A19 Proin a browser tab · 16 November 2026not timed<0.010.02
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed<0.010.01

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. A phone as a clicker for slides or a show
  2. Pairing a phone with an app on the LAN
  3. A local control page for a tool or kiosk
  4. Speaker notes and a timer on a phone
  5. Rehearsing a remote without a network
  6. A QR code for a local link

Pitfalls, in brief

  1. This is plain HTTP on a trusted local network.
  2. Phones only reach the server when it listens beyond loopback: vite --host (or server.host: true), or listen on 0.0.0.0.
  3. The Host header must be localhost, 127.0.0.1, [::1] or one of this machine’s LAN addresses (DNS rebinding protection).
  4. Sessions start only from loopback (127.0.0.1 or ::1): the presenting page must be opened as localhost on the machine itself, not by its LAN address.
  5. Everything lives in the server’s memory.
4 more in brief
  1. The state you publish goes to every paired phone four times a second: words only, small (the Node adapter refuses bodies over 64 KB).
  2. Commands expire after 2 s and the presenter drops any that arrive late, so a stalled tab never jumps two slides when it wakes.
  3. A phone keeps its token in sessionStorage: a reload stays paired, a closed tab pairs again.
  4. Web Crypto (globalThis.crypto) is needed for the codes and tokens: Node 20 or later, any current browser.
9 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From My other apps. Fully custom code.

ISO/IEC 18004:2015, QR Code bar code symbology: the QR encoder copied from the library’s audience-vote entry, written from the standard

WAI-ARIA Authoring Practices Guide (W3C): buttons that stay focusable while unavailable (aria-disabled), alerts for errors, and a polite live region for steps and pairing. Written here from scratch.

Fetch Metadata Request Headers (W3C): Sec-Fetch-Site: cross-site is refused, beside the Origin and Host checks

remote controlpresentationclickerpairingQR codeone-time codelockoutconstant-time compareDNS rebindingsame-originlocal networkLANWi-FipollingdeduplicationexpiryNodeVite pluginmiddlewarelive regionaccessibilitykeyboardtouchdom

Near it in the frame