Device status that ages with the connection.
Help operators understand which devices are available.
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 worked on device heartbeats, reconnection state, and cleanup of stale connections. The fleet view needed to stop treating an old connection as an active player while retaining useful device context when it reconnected.
Connect a control with the receiving device
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
- DynamoDB
- Store and retrieve device or application records using defined access patterns.
- Authentication
- Establish who is making a request before applying account or access rules.
- Scheduled jobs
- Run time-based work without waiting for a person to open the application.
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.
- Inactive-device detection
- 20 secTime to detect inactive devices through real-time health monitoring.