Getting Started with signageOS Open

blog-signageos-open

The launch of signageOS Open is finally here! We are extremely excited to get companies started using this innovative technology. So, how does this happen? We will be releasing portions of signageOS Open in waves. This is to allow companies to explore the proprietary code and familiarize themselves with our framework before deploying devices with signageOS integrations. Also, this better prepares companies for using signageOS Open long-term. 

Below is an outline for the launch and release of signageOS Open. We are currently in Step 1 and will progress as companies familiarize themselves with the signageOS technology. 

You can expect Step 2 to be released in 4 weeks which will then allow you to proceed to Step 3 & 4 immediately. 

1. Explore Documentation

Specific parts of the signageOS Documentation related to signageOS Open are now available. Once you log into the signageOS Open Documentation, take some time to explore the framework and developmental logic. Inside the current signageOS Open documentation, you will find information on the unification API, changelogs, and images to assist in development.

  • JavaScript API includes information on the content-playback (video playback, file systems, offline caching, and much more) and device management.
  • Changelogs include changes to the API, front-applet, front-display, and device integrations.
  • Device provisioning or deprovisioning according to device type and desired functionality.

What you can expect to be added:

  • Additional Knowledge-base information regarding compatibility, tutorials, use-cases, etc.signageOS-open-getting started

2. Implement JavaScript API

Using the signageOS SDK, implementing the JavaScript API is as easy as 1,2,3. In Step 2, implementation of the JavaScript API will be made available as well as support for popular IDE's like VS Code. 

In the documentation there are step by step instructions regarding the JavaScript API for different content playback properties like handling web browsers, commands, file systems, inputs, loading fonts, timing, syncing, and much more.JavaScript_API_reference_signageos_Open

3. Deploy Devices

Provisioning and deprovisioning devices is done through the signageOS Box (device management console). This process is very straightforward but varies according to the hardware that is being provisioned. Within the documentation are step-by-step instructions for connecting each device with signageOS.

Device_Provisioning_signageOS_Open

Generally the provisioning process consists of three main steps:

  1. Generate your Open Core Apps within Box

  2. Upload the Open Core Apps onto your server

  3. Install the Open Core App onto the device

4. Profit

The last thing to do is to build diverse networks of varying hardware and profit. signageOS Open requires some development time but offers tremendous potential to CMS companies.

Support is not included to those using signageOS Open. We have provided the tools to build and now it is up to you to complete the task. However, in case you experience any issues, signageOS can assist and provide paid support. If support is needed, contact support@signageos.io and we will contact you regarding available support plans for signageOS Open. 

Insider digital signage signageOS Updates Change Logs Documentation signageOS Open

Subscribe Here!