Content guidelines and restrictions for BrightSign client
The Wallboard client, made for BrightSign devices, is built entirely in HTML, and all contents and pages rendered in it must comply to the HTML Best Practices guidelines, provided by BrightSign, in addition to the following recommendations to ensure the best rendering performance and display quality.
If you are able to choose which BrightSign products to use, we recommend the XT or XD product lines for maximum performance.
We have constant ongoing optimizations in the content rendering interface (so-called displayer) and we are developing a new displayer, specialized to simple content playback with significantly improved speed.
You can find the recommendations below for each widget in our editor.
Stationary text is among the easiest contents to render and in itself it doesn’t cause any issues, however it can have an impact on speed if it has an animation or effect (such as drop shadow) added to it or is placed above or behind another animated widget. This impact depends on the amount and size of the text, and the complexity and motion of the animations involved.
If you experience playback speed issues, consider reducing or removing the mentioned factors.
Similarly to the text widgets, stationary images have low performance impact, but they can have more influencing factors. In addition to the animations and effects attachable to text widgets, images can have relatively big file sizes which not only affect network usage, but they can slow down page swaps if the overall size or number of images, needed to be shown at once, is too big. If you are concerned about file size, try to improve the compression ratio by converting the images to jpg or png format.
Semi-transparent or animated gif images can take additional resources to play.
Images that are resized in the editor can also cause additional computation for the browser to render, try to use the images in their native resolution, and always consider the absolute maximum resolution allowed for each BrightSign device described in the best practices document linked above, otherwise the image is not rendered at all.
Videos also have the same influencing factors as images, but they can be even more impactful.
Videos have a frame rate property which determines how many frames needed to be rendered per second. Higher framerate both makes the file size bigger and the playback more resource consuming. If you experience issues convert your videos to lower resolution, frame rate or use a codec with better compression ratio.
We recommend that if you want to display high-resolution video(s), then minimize the amount of any other widgets on that page.