The Rx Workflow Pattern
summary
Square’s Point of Sale app has ~300 screens touched by almost 200 engineers, with clean builds up to 12 minutes; the fix is to split business logic into reusable bricks and UI/state logic into composable Workflows that expose immutable inputs and reactive outputs (using RxJava or similar). Workflows emit typed screen objects (key + observable view state + event interface), bind to platform coordinators, drive a tiny finite‑state machine DSL, compose hierarchically, and let pieces run and test in isolation; nine months into a planned two‑year refactor.
AI-written summary · about
chapters (7)
- 0:00Introduction and problem overview
- 9:25Futures team and vision
- 17:13Core principles and architecture
- 23:18Bricks pattern explained
- 28:59Workflows pattern explained
- 37:02Real-world workflow integration
- 39:26Summary and next steps
related talks
47mThe Reactive Workflow Pattern Update
41mSquare Workflow: Android and iOS apps composed of state machines defining UI and navigation.
34mReactive Workflows a Year Later
28mApplying Rx Best Practices to Your Architecture
37mA Practical Guide To master Rx Streams
51mManaging State with RxJava
42mHands on MvRx: Building Real Apps
34mEffective Reactive Architecture