Implement parent device: receive and render streams #5

New issue

Open

opened 2026-09-02 15:25:38 +02:00 by emidab · 0 comments

emidab commented

2026-09-02 15:25:38 +02:00

Owner

Summary

Implement the parent-device (held by the parent) responsibilities: receive, decode, and render the child's streams with per-stream receive toggles.

What to do

Parent app shell screen (runs the parent role)
Receive and play audio stream
Receive and render video stream — each independently toggleable on the receive side
Receive sensor telemetry feed
Handle buffering, latency, and connection/reconnect states in the UI

Acceptance criteria

Parent can toggle audio playback on/off independently
Parent can toggle video rendering on/off independently
Audio and video play from the child over the secured connection
Receive-side failures and buffering are surfaced clearly
Tests use fakes (no real network in CI)

Notes

Depends on networking arch, mTLS/connection, and child-side transmit
Keep receive toggles decoupled so toggling one stream doesn't affect others

## Summary Implement the parent-device (held by the parent) responsibilities: receive, decode, and render the child's streams with per-stream receive toggles. ## What to do 1. Parent app shell screen (runs the parent role) 2. Receive and play audio stream 3. Receive and render video stream — each independently toggleable on the receive side 4. Receive sensor telemetry feed 5. Handle buffering, latency, and connection/reconnect states in the UI ## Acceptance criteria - [ ] Parent can toggle audio playback on/off independently - [ ] Parent can toggle video rendering on/off independently - [ ] Audio and video play from the child over the secured connection - [ ] Receive-side failures and buffering are surfaced clearly - [ ] Tests use fakes (no real network in CI) ## Notes - Depends on networking arch, mTLS/connection, and child-side transmit - Keep receive toggles decoupled so toggling one stream doesn't affect others