UI's Across Multiple Devices
summary
Describes a Polymer-based cross-device library that synchronizes state with an xdmvc-synchronised element, uses WebRTC peer-to-peer for low-latency device-to-device updates, and assigns UI parts via a controller-layout/dom-if pattern; pairing is done by QR code URL pairing (url-pairing component). Demonstrates a webcam viewer implemented in under less than 300 lines server+client and a mountain-bike trip planner built by students in 14 weeks (≈300 hours each). Components work across phones, tablets and large screens and students become productive quickly.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:02Distributing the UI
- 3:21Pairing Devices
- 4:49State Synchronisation
- 6:53UI Distribution
- 9:49Data-Binding
- 9:59Conditional Templates
- 10:10Modularity
related talks
28mDynamic UI at the Edge
34mA conceptual future for the multi-device web
20mXDBrowser: User-Defined Cross-Device Web Page Designs
23mJSConf 2015 Chris Lorenzo
36mBuilding framework agnostic UI with Web Components
33mBuilding with Web Components using X-Tags
23mBuilding a custom library for videochat with Svelte's Web Components Support
19mWeb Components
