Feature entitlement: devSpace · Availability: DevSpace

Deploy an applet on a device

Your Applet can have multiple versions. You can deploy any version of your Applet to any devices, as you need. Applet version is defined in package.json.

package.json

{
	"name": "your-applet-name",
	"version": "0.0.1"
	/* ... */
}

Whenever you upload an applet to signageOS, a new version is created which respects the version in package.json. If the version already exists it can be overwritten if the version is still draft. Once a version is published it can no longer be overwritten — see the Applet Version Lifecycle guide for publishing, deprecating, and renewing versions.

Limiting supported platforms for your Applet

You can define a list of supported platforms for your Applet. Adding supportedPlatforms configuration into package.json limits available building target on the Smart Builder page.

package.json

{
  /* ... */
	"sos": {
		"supportedPlatforms": ["tizen", "webos", "brightsign"]
	}
  /* ... */
}

Options to select from:

• android
• brightsign
• chromeos
• tizen
• webos
• windows
• linux

By default, Applet will be available to be built on all supported platforms.

Deploy to a device

There are 2 ways how to deploy an applet to a device. Either it can be deployed using CloudControl or it can be bundled into a native application.

• To deploy the applet using CloudControl follow How to assign Applet to the device via Timings. This method assigns applet versions directly to devices — no native app generation required and no build quota consumed. You can reassign new applet versions at any time.
• To deploy the applet as a native application use SmartBuilder. This is typically used as the final production deployment step. See the Applet Development Workflow for the recommended development and testing process before using Smart Builder.