Remote controls with per-device results.
Give operators clearer control over playback.
Where this work fits
An operator might need to pause several players or change a venue’s volume. Some devices could be connected while another was unavailable. A dashboard needed to make that situation understandable.
I built WebSocket playback controls for individual players and groups of devices in a venue. A group operation could reach some devices while another was unavailable, so its result needed to preserve that distinction instead of returning one blanket success.
Connect a control with the receiving device
Sending a command does not mean the player received it. Connection feedback shows when playback can be controlled and when the device is unreachable.
A group command can have mixed results.
One unavailable device should not erase successful sends to the others. I returned per-operation delivery results and worked on aging connection state so a disconnected player would not look active indefinitely. A sent command still needed to be distinguished from observed playback.
The skills behind the work
- WebSockets
- Carry interactive messages between connected clients and backend services.
- DynamoDB
- Store and retrieve device or application records using defined access patterns.
- Error recovery
- Handle interruptions and failed operations without discarding useful progress.
Operators could control players remotely and see more useful information about their availability. The backend supported venue-level actions without treating the entire fleet as one device.