signageOS Frequently Asked Questions

Smart displays and media players are produced with different firmware versions far more rapidly than their life expectancy. Integrating newer and older firmware versions requires bug fixes, updates, testing, and much more. This is a very timely and costly process. signageOS not only provides the integrations, but also maintains the integration so you don’t have to. Our ultimate goal: Bringing you a complete Backend as a Service(BaaS) solution designed for digital signage.

Frequently Asked Questions

signageOS uses a built-in failsafe that caches previously uploaded content. In the event of connectivity failure, the device will display the previously cached media until the device goes back online. The CMS has full capability to determine what will be cached and what will not.

The applet is the HTML5 player/application used to play content on registered devices. CMS companies develop custom HTML5 players to display their content with the JavaScript unification layer provided by signageOS.

Develop your unique CMS features within an Applet version to display the content to the end-user. Create a new Applet version to apply major changes to the previous Applet. Applet versioning helps keep track of the continuous changes made to each new Applet version.

Yes, signageOS does not interfere nor limit the feature and playback variations offered by the CMS company. Freely develop and create as many Applets as desired for each organization.

Each Organization is a group of devices that belong to the same end-customer. Each device can have only one organization.

Yes, you can assign the same Applet to as many organizations as you would like.

  1. Sign up and get full access to signageOS Documentation
  2. Build/adjust and test HTML5 player using signageOS API
  3. Deploy any SoC display or media player into the network

signageOS fully supports white labeling by the CMS.

The CMS/partners will not be able to view any signageOS branding if they do not want to. The only persons that will be able to view the signageOS branding are the persons that integrate the CMS with signageOS.

No. All content and data stay inside your CMS and are transported to all your connected devices directly.

signageOS does support hardware specific features. Examples of hardware specific features include: remote firmware upgrades, enhanced pin security, custom alerts, status reporting, internal memory status, and much more.

signageOS can automatically update the platform to reflect new versions or updates for every major device type based on the desires of the CMS. As new firmware versions are released, signageOS tests and analyzes the benefits of the updated firmware. If the firmware updates enhance the functionality of the displays, the updated firmware will be certified and recommended to the CMS.

Less than 4GB.

signageOS has failsafe protocols that store data on the devices in the event of the device going offline. If the device goes offline the cached content will still be displayed. Also, signageOS routinely tests for availability and scores are consistently 99.7% or higher, including scheduled maintenance.

Native applications crafted for each platform are able to recognize when a compatible device is available. The verification process allows for the recognized devices to then be securely added via verification hashes. Once verified, the device is then ready for full management control over the API or within the Box.

No, no proprietary components by Samsung or LG are used in conjunction with signageOS. All data traffic between the client and signageOS are encrypted and checked for security, validity, and reliability using multiple methods. All management and monitoring features are built-in and completely developed by signageOS.

Yes, using REST API functions you can automate changing Applets.

No, there is no hard limit on Applet size; however, media should be pulled from other sources so the Applet does not contain too much data.

CMS companies that have the development capacity to use the signageOS JS API to develop heavily on the backend on their own. signageOS Open provides the CMS company with the proprietary API for any integration with a limited device management UI. signageOS offers paid support to Open users.

  1. Sign up and explore documentation
  2. Implement javascript API
  3. Deploy devices

Still have questions? Get in touch