[Emulator] Rejected non-SSL request from Applet
Explains why the signageOS Emulator rejects non-SSL requests from an Applet and how to resolve it with a reverse proxy or by switching the Emulator to plain HTTP.
Explains why the signageOS Emulator rejects non-SSL requests from an Applet and how to resolve it with a reverse proxy or by switching the Emulator to plain HTTP.
Enabling native debug on Android-powered players and displays will allow you to access WebView console and capture logcat logs during development.
How to remotely debug Applets on devices using Weinre, enabled from the Box Troubleshooting tab to inspect DOM and console logs over websockets.
Compares five Applet deployment options, from manual hosting and 9900.io provisioning URLs to CloudControl Device Policy, Bulk Provisioning, and REST API automation.
The complete applet development lifecycle — from local development to production deployment. Learn how to iterate freely without consuming your build quota.
Overview of platform-specific Native Debug for Applets, activated via Box or REST API, with Chrome inspector steps for Tizen, webOS, Android, and more.
Manage the lifecycle status of an applet version — publish a built version, deprecate a broken or obsolete one, and renew it — from the CLI, SDK, or REST API.
You can add a number of key-value pairs into the Applet in a form of config.
NOTE: Enabling native debug on Brightsign devices causes memory issues and may lead to out of memory errors, make sure that Native debug is turned off...
This provisioning is mandatory for any device running on the free Device Plan Open; optionally, this process is also available for any device under any...
NOTE: Enabling native debug on ChromeOS devices causes memory issues and may lead to out of memory errors, make sure that Native debug is turned off...
Describes the Core App connection to the signageOS License server, what telemetry is gathered, and how to opt out with a perpetual license key.
How signageOS synchronizes playback across multiple devices for video walls and menu boards using a Peer2Peer JS API, with network requirements and setup steps.
Step-by-step guide to creating, running, and deploying your first signageOS applet — from project setup to testing on a real device.
Your generated Core Apps will be automatically assigned to the Organization under which you developed your Applet in the device-app builder.
Command line tool for rapid local development brings you the ability to easily start developing on top of signageOS framework from your favourite IDE.
Explains corner-pixel status indicators and Debug Mode icons that reveal device connection, authentication, verification, and Applet loading states on the display.
The Emulator is a web-based application that emulates the behavior of physical devices and the signageOS JS APIs.
Explains the Blob not found error on startup of large Applets, caused by generating a Core App before the build finishes, and how to avoid it.
Collection of signageOS example applets demonstrating video playback, HTML overlays, touch input, and multi-screen synchronization.
Compares the File System API and File Cache API for storing files in Applets, covering external storage, available space, cache clearing, and Power Action effects.
Expose a local HTTP server to the internet via a WebSocket tunnel. Used internally by signageOS CLI and SDK for device connectivity during local development.
Applet JS SDK provides device's native features and functionalities with unified API for all supported platforms. This SDK is only usable
If you want to develop applets with React JS you can follow this example. This tutorial explains you how to set up Create React App and create the first applet.
If you want to develop applets with Vue you can follow this example. This tutorial explains how to set up Vue and create the first applet.
How to enable and use developer debug mode on LG webOS displays for signageOS troubleshooting.
How to debug a Linux signageOS device by enabling Native Debug in Box and connecting Chrome DevTools remotely via chrome://inspect on port 9992.
Deprecated comparison of signageOS Open and Cloud-connected Platform plans, features, and pricing.
Native debug on RPi3 requires you to install Epiphany Browser (a.k.a. Gnome Web) on your PC.
Step-by-step guide for native debugging on Samsung Tizen 3.0+ (SSSP5 and above) displays using Developer mode.
How to use the Applet Commands API to log events from devices, retrieve them over REST API, and send real-time messages from your server to devices.
Smart Builder is part of DevSpace - developer platform to build HTML5/Javascript apps with native device/hardware functionality.
Lists device platforms supporting sensors, including Raspberry Pi firmware requirements and Nexmosphere serial-port compatibility on Android, Windows, and Tizen.
How to transpile Applet JavaScript to ES5 for older WebKit-based SoC devices, using automatic transpilation in the Web Editor or Babel in CLI-based projects.
This process is mandatory only for any device running on free Device Plan Open;
Native video playback in background was successfully implemented on LG webOS, Samsung Tizen, BrightSign, Windows, and Android.
How to debug Applets on Windows devices via Chrome inspector on port 9222, including legacy Kiosk-mode steps, password recovery, and troubleshooting tips.