Server-Sent Events on Android: Real-Time Streams That Surv…
summary
Industrial Android dashboards use Server-Sent Events with a clear, production pattern: four pull requests fix three connection leaks in the Rage Ruby SSE server (all merged), OKHttp5 SSE is only a parser while Ktor provides reconnection, and the read timeout 10s trap breaks long streams. The client implements a state machine with watchdog timer, jittered exponential backoff, offline ring-buffer replay and last-event-id resume so one-way monitoring survives shift-long Wi‑Fi outages.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:45Why SSE matters in Android
- 4:33Seven SSE topics on Android
- 8:45Android’s SSE reconnection gap
- 10:52Silence in streams and heartbeat
- 13:23Ruby’s SSE lessons
- 17:36Android SSE survival kit
- 22:35Offline handling in real-time
- 25:44Backpressure and state machine
- 26:50SSE vs WebSocket for monitoring
- 29:05Q&A
related talks
14mReal-Time Communication in Android
20mHow to build a Clean SSEClient Flow
39mReactive Android: RxJava and beyond
40mAndroid high performance baby
19mSolve your Mobile Bugs with Session Replay
37mAndroid Industrial: Real-time data visualization
34mReal World Android Akka
19mLazy Robots: Telemetry Buffering on Android