Decoupling with Google Polymer
summary
Comcast builds multiple production apps (X1, X5, Xfinity Home) with Google Polymer web components, Redux for state, and a JAMstack static front end that deploys in minutes and separates UI from APIs. Polymer 3 moves to ES6 modules but migrating older Polymer 1/2 code is painful; IE11 support forces transpiled builds. A reusable XE header custom element ships to millions of devices daily. Performance wins are concrete: mobile pages lose 53% abandon rate over 3s and 1s speedups raise conversions ~27%.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:25Coding Journey
- 7:11Encapsulation Composition Separation of Concerns
- 11:13Performance Matters
- 21:33Programmers know the benefits of everything and the tradeoffs of nothing.
- 28:16App Shell Architecture
- 29:37CRITICAL PATH 1. Authenticate 2. Make API Calls 3. Load View
- 33:58Demo Driven Development
related talks
10mChris Lorenzo at The Lead Developer New York 2017
29mPolymer in Practice
23mJSConf 2015 Chris Lorenzo
28mPolymer and Web Components
01h 00mAn Introduction to Web Components and Polymer
01h 48mIntro to Web Components & Polymer Workshop
51mOutrun the 🐻! Performance Optimizations for Progressive Web Apps
14mOpening Remarks