UX as an API
summary
Argues that APIs should ship white‑label UI fragments alongside data, demonstrates building a progressive web app by composing web components (lit‑element), documenting them in Storybook, and theming via CSS custom properties and the new ::part selector. Shows a chatbot fragment integrated into a site, then restyles it to match the host. Notes gotchas: CORS for module imports, dependency collisions (rollup recommended), bundle size and performance, and unresolved security/trust boundaries for auth/payment.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:53William Bartlett
- 1:28Mandatory Hand Raising Time
- 6:11The Goal
- 6:54Micro-frontends
- 7:33Third Party APIs
- 10:40Examples Embedding
- 13:25Related Solutions
- 16:04Web Components
- 44:59Gotchas
- 46:17Conclusion
- 47:02Going Further
related talks
27mUser focused API Design
01h 03mEvolving compositional user interfaces
44mThe Future is in Pieces
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
49mUX Engineer, engineers connecting design and front end
58mChasing the holy grail: reusable web components and design tokens
41mComponents Approach to Building Web Apps
44mMake UI Components for the Web Framework Ecosystem
