VISUALIZING KOTLIN FLOW IN ANDROID
summary
Shows how Kotlin Flow values move with animated visuals, a demo Android app mapping three Chicago landmarks, and an extension library called meteor that autogenerates those animations; demonstrates that regular State Flow is hot and unavoidably conflates slow collectors (causing a missed Lincoln Park Zoo), and that Shared Flow can be configured to wait for slow collectors so no events are dropped; explores flatMapMerge and worker‑pool patterns and builds working examples that expose pitfalls and fixes.
AI-written summary · about
chapters (26)
- 0:00Start
- 3:18Asynchrony
- 4:02Reactive Streams
- 4:34Clean Architecture
- 5:20Ergonomic
- 6:15Suspension
- 7:27Structured Concurrency
- 8:13Share by Communicating
- 9:35Cold, Non-Blocking Data Streams
- 12:41it's Structured!
- 15:10Navy Pier
- 15:51Adler Planetarium
- 16:05One Map
- 17:21Data Models
- 18:09Observe the locations
- 20:26this sounds familiar.
- 21:48List Locations
- 22:56Chart Locations
- 24:20What if we move too fast?
- 26:42Shared Flow
- 29:25Cold Flow Animation
- 32:20Concurrent Flows
- 34:26ChannelFlow
- 36:17What can we expect?
- 37:57Photo Credits
- 38:08Beyond the talk
