Data Flow in Polymer Elements and Apps
summary
A live chat-view demo implements both distributed bidirectional bindings and a centralized unidirectional model so you can compare trade-offs: bidirectional uses Polymer’s nonstandard mutation helpers (this.push, this.set) and deep observers, while the centralized version uses one-way bindings, events or function callbacks, an immutable update pattern (Object.assign, slice) and a Redux-backed store via the Polymer Redux library. The claim is that two-way bindings are fine for local scalar sync, property effects remain lightweight, and the alternative app versions work and are on GitHub.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:22Data Flow
- 1:06Unidirectional Data Flow
- 2:47Thinking in Polymer
- 3:24Chat Demo
- 3:54Components
- 4:58Custom Elements
- 5:32Purpose in Life
- 5:53Declarative Format
- 6:34Mediator Patterns
- 7:37Dataflow
- 8:12Input Header Template
- 8:57Data Flow Visualization
- 9:25Input Header
- 10:55Event Listener
- 12:18Twoway bindings
- 13:46Onward and app
- 13:58App model
- 15:16Mutations
- 15:59Distribution of Responsibility
- 19:10Push Notifications
- 19:50Complex Observer
- 20:40Unidirectional Approach
- 20:57Event Fire
- 21:32App Template
- 22:14App Logic
- 24:30Polymer Redux
- 24:46Polymer 20 Changes
- 25:39Takeaways
- 26:00Outro
related talks
37mA look at the guts of Polymer 2.0
31mApplying Unidirectional Data Flow Beyond the ReactJS Ecosystem
26mInteraction Design with Ember 2.0 and Polymer
34mFunctional UIs and Unidirectional Dataflow
14mUI's Across Multiple Devices
19mWeb Components
33mEnd to End Apps with Polymer
41mComponents Approach to Building Web Apps