Improving the Android player update process

Feature Requests
1

Updating our Android players currently requires several manual steps:

  1. Downloading the latest APK
  2. Uploading it to the Player Versions section
  3. Assigning that version within the display settings.

A nice to have feature would be to introduce one of the following 2 ideas:

  • Let the CMS automatically check for updates with a 24h or interval.
  • Introduce a button to manually check for updates.

Once the CMS detects that there is a new version available, it should then automatically proceed to download it to the player versions, and update the default display setting for the Android player with the latest version.

On top of that, it would be nice to introduce the following configurations:

  • Wait (x) days before installing a new release
  • Configure a specific display group to be automatically updated
4 Likes
2

I support this idea. Automating Android player updates would save time, reduce manual work, and help keep devices up to date. Features like automatic update checks, delayed deployments, and targeted updates for specific display groups would provide both convenience and greater control over rollouts.

3

How would one go with updating 3rd party player over Xibo CMS ?

1 Like
4

I would think adding a configuration where you’d put in the URL of the 3rd party, and instead of checking on Xibo, it will check using the link provided.

1 Like