Streaming-only playback has a visible failure mode
If every loop requests media from the internet, a short branch outage can become a blank or frozen public display. Local media removes that dependency from normal playback.
Playback reliability
Veysign is designed so routine playback does not depend on a continuous connection. Each Android player stores the complete assigned playlist, keeps using the last working version while offline, and changes versions only after the next update is ready.
Why teams change the workflow
If every loop requests media from the internet, a short branch outage can become a blank or frozen public display. Local media removes that dependency from normal playback.
The safe response to a failed download is to retain the complete playlist already on the device, not switch to a version with missing files.
The player reconnects for new assignments and status. Operations still need to investigate a device that remains offline long enough to miss planned changes.
Implementation
The dashboard resolves which playlist and schedule apply to the device, group, or location and makes a new manifest available.
The player retrieves media that is not already available locally while the current approved playlist remains usable.
Only after the new version is complete does it become the active playlist, avoiding a half-downloaded public display.
During an outage the local playlist continues. When connectivity returns, the player reports status and checks for newer work.
Product fit
Images and videos already stored on the device continue according to the active playlist and schedule.
The player can move through previously received scheduled content using its local clock and configured timezone information.
A failed or interrupted sync leaves the last complete content version available instead of deleting it first.
New uploads, changed assignments, and fresh status require reconnection; they resume rather than retroactively appearing while offline.
Offline playback protects the audience from a short connection problem, but operations should still define how old content may become. A permanent pricing change, urgent closure, or safety message cannot reach a disconnected screen. Monitor last contact and set an escalation window appropriate for the business.
Test storage capacity as part of playlist design. High-bitrate or long videos require more space and more download time before a safe switch can occur. Keep assets appropriate for the player hardware and remove media that no longer belongs in active content workflows.
Use evergreen fallback material whenever possible. If a short campaign ends while a device is offline, a previously downloaded default playlist gives the schedule useful content to return to. Review schedules around timezone changes and test the expected transition without connectivity.
Content that has already downloaded to the Android player continues playing offline. Initial activation, new content, changed assignments, and remote status require connectivity.
The player retains the last complete playlist. It does not replace working content with a partial version and can resume update work after connectivity returns.
Previously received schedules and media can continue to resolve locally. A schedule that refers to content the player never downloaded cannot be introduced until it reconnects.
Review device status and last-contact information in the dashboard. Define an operational threshold for follow-up based on how quickly that screen’s content normally changes.