How to build a Clean SSEClient Flow
summary
Claim: a Kotlin-based client uses Server-Sent Events (SSE) + StateFlow inside a Clean Architecture to deliver real-time updates with minimal complexity. The system opens one SSE HTTP stream, exposes a hot StateFlow from the data layer, and propagates parsed events through repository and use cases to ViewModel and UI. A sample app is implemented and ported between Just Eat Takeaway and Just Eat for live order and driver location tracking, it continuously receives many events and the demo shows it working reliably.
AI-written summary · about
chapters (7)
- 0:00Introduction and use cases
- 1:49Choosing client-server communication
- 6:23Clean architecture layers
- 9:52Streaming data options
- 15:55Implementing StateFlow
- 17:39Sequence diagram walkthrough
- 19:46Closing and resources
related talks
31mServer-Sent Events on Android: Real-Time Streams That Surv…
14mReal-Time Communication in Android
49mRiding the state flow
49mLearn you advanced Akka Streams for great Good!
49mKotlin Reactive Programming Patterns
29mKotlin State & Shared Flows in Action
36mMigrating to Kotlin State & Shared Flows
25mKeeping Up Continuous Development of BLE-Based Apps