Have more questions? Submit a request

Applet Deployment Options [GUIDE]

  1. signageOS
  2. DevSpace Guides
  3. Getting Started with Applets

Applet (your HTML5 application with signageOS JS SDK) can be deployed to supported devices in several ways. This article describes each option in detail, including the pros and cons.

Options Overview

Deployment options for Applet range from very manual steps to a fully automated process. Here is the high-level list:

A) Manual deployment and application hosting

B) Deployment with hosted provisioning URL

C) [CloudControl] Deployment via Box and Device Policy

D) [CloudControl] Bulk Provisioning

E) [CloudControl] Automated Deployment via REST API

Options A) and B) are available out-of-the-box with DevSpace. Options C), D), and E) require a CloudControl subscription (purchased by you OR your customers)

 

Each of the options is described in greater detail below. For each option, there are the following prerequisites:

  • You have an active DevSpace account and subscription
  • You have created your Applet and uploaded it to your DevSpace account
  • Your Applet successfully compiled and is ready to be built for the target platform

A) Manual deployment and application hosting

When to use

This option is best for DevSpace users that want to host the final application builds on their own servers/domains with no affiliation to signageOS.

Pros

  • applications are hosted on your own domain
  • deployment works 100% offline with no dependency on an Internet connection
  • suitable for on-premise/secluded networks deployments

Cons

  • you need to manually download applications from DevSpace and re-upload them to your servers
  • less flexible
  • you have to make sure you keep the right folder structure, otherwise, the deployment will not work

How to use this option

  1. Open your DevSpace portal and navigate to the Smart Builder section
  2. Select "Generate Deployment app"
  3. Select target platforms and optional configuration for your Applet
  4. Initiate the build by clicking the "Generate" button

Once the build is completed follow the next steps:

  1. Click on the View Build icon in the list of your latest builds
  2. Select Download Build and save the zip file on your computer
  3. Unpack the zip file and upload all files to your server
  4. Validate that all files and folders are accessible over the network
  5. Continue with the provisioning guide for the selected device 

Device-specific notice

  • Samsung is very diligent with the exact folder structure, always keeping the files as-is
  • Android-based platforms include *.apk files that you can sideload to  devices over USB without the need to upload the build to any server
  • SONY has to be additionally signed prior to deployment, reach out to our support team to learn more

B) Deployment with hosted provisioning URL

When to use

This option is best for DevSpace users that want to distribute the final application builds immediately and hassle-free on a white label domain 9900.io provided and operated by signageOS.

Pros

  • applications can be distributed immediately
  • no need to manage application hosting and validate folder structure
  • valid SSL certificate for legacy devices
  • 9900.io is easy to enter via IR remote control on OSD keyboards
  • compatible with 3rd party tools like BSN.cloud, Samsung TBM and MagicInfo

Cons

  • applications are available on the 9900.io domain
  • an Internet connection has to be available to use this deployment method

How to use this option

  1. Open your DevSpace portal and navigate to the Smart Builder section
  2. Select "Generate Deployment app"
  3. Select target platforms and optional configuration for your Applet
  4. Initiate the build by clicking the "Generate" button

Once the build is completed follow the next steps:

  1. Click on the View Build icon in the list of your latest builds
  2. Copy the provisioning URL (e.g.: 9900.io/aaBBcc)
  3. Continue with the provisioning guide for the selected device 

Device-specific notice

9900.io URLs can be used to provision via 3rd party tools:

C) [CloudControl] Deployment via Box and Device Policy

When to use

This option is best for users that are using CloudControl for device management. CloudControl subscription can be either owned by your company or by the end-user.

Pros

  • no need to generate the native applications, Applets are deployed directly from the cloud
  • it's easy to set and later adjust the Applet configuration or Applet version
  • more scalable option while using Bulk actions or Device Policy
  • compatible with 3rd party tools like BSN.cloud, Samsung TBM and MagicInfo

Cons

  • device has to be already provisioned with signageOS Core App
  • requires connectivity to signageOS at the time of the deployment

How to use this option

There are multiple options on how to assign Applet via Box. You can use all of them as each provides benefits in specific scenarios.

One-by-one steps

Best for manual deployments, testing, or device swaps.

assign-applet-device-detail.gif

    1. Open Box (CloudControl UI)
    2. Navigate to the Device detail of your selected device
    3. Go to the Timing section
    4. Add/modify a Timing
    5. Within the form find the Configuration section
    6. Add your key-value pairs
    7. Save Timing

 

Device policy

Best for pre-configuring your Applet and then apply to any device enrolled under signageOS CloudControl.

  1. Open Box (CloudControl UI)
  2. Create or open a Device Policy
  3. On the Applet tab select the Applet, version, and configuration you want to apply
  4. Assign that Device policy to the selected device(s)

D) [CloudControl] Bulk Provisioning

When to use

The best option for CloudControl users that are deploying a large fleet of devices that are already known (either it's a takeover project or you know the list of devices with their specifics). The applet is assigned via the Device policy at the time the device first connects to the signageOS cloud.

Read more details about Bulk provisioning here.

Pros

  • no need to generate the native applications, Applets are deployed directly from the cloud
  • scalable solution ensuring consistent results and configuration
  • compatible with 3rd party tools like BSN.cloud, Samsung TBM and MagicInfo

Cons

  • devices have to be first enrolled in Bulk provisioning using their serial number or MAC addresses
  • requires connectivity to signageOS at the time of the deployment

How to use this option

  1. Open Box (CloudControl UI)
  2. Create or open a Device Policy
  3. On the Applet tab select the Applet, version, and configuration you want to apply
  4. Navigate to Bulk provisioning
  5.  Upload a list of your device with serial numbers/MAC addresses AND the device policy you have set up

Once any of the devices reach the signageOS cloud for the first time, it gets automatically configured and set up.

E) [CloudControl] Automated Deployment via REST API

When to use

The best option for automated workflows and customized steps. This option requires the development and usage of signageOS REST API.

Pros

  • fully customizable steps and per-device configuration
  • universal REST API works for all supported devices
  • ability to connect the provisioning with your or 3rd party tools

Cons

  • requires connectivity to signageOS at the time of the deployment
  • requires development

How to use this option

  1. Learn more about available REST APIs: https://api.docs.signageos.io
  2. Check a quick start guide or Getting started guide

 

 

Was this article helpful?
0 out of 0 found this helpful
Share