...
Partners can use our APIs to connect their CMS directly to the Control Cloud. This enables , enabling their CMS to be used as the user interface for player provisioning.
Once created, Setups can be applied to a player or group of players using BrightAuthor:connected or control.bsn.cloud. Alternatively, the information contained in a Setup information can also be directly incorporated into the Player App (described below) and then manually copied to the player’s storage device.
...
The set of files and folders that instruct the player what to do upon boot up is collectively known as the Player App. At a minimum, the Player App must contain an autorun.brs file (the .brs extension denotes a BrightScript file).
...
Partners can write custom Player Apps to perform certain actionsaccording to their specific needs. For example, the Player App may be designed to connect to the partner CMS to download content for the player to display. Many partners use our basic autorun.brs as a foundation for writing their own Player App.
...