ScreenSoft Docs / Applications

Applications

Extend screens with interactive, content, web, game, camera and other application-layer functions.

Application library

Open My applications and use the + button in the lower-right corner to select an application type. The library evolves over time and custom applications can be developed for project-specific requirements.

Presentation and Application layers

Campaigns belong to the Presentation layer. Applications belong to the Application layer.

The Presentation layer is used for automatically played content such as campaigns, advertising, information visuals and notices. Content plays according to its configured period, targeting and rules without requiring visitor interaction.

The Application layer is the interactive part of ScreenSoft. Visitors actively open and use web pages, galleries, documents, videos, quizzes, Wheel of Fortune, 3D Maze and other applications. It is typically used on a touch screen; some applications can also be controlled from a mobile phone through a QR-based scenario.

A device can use both layers or only one. When both are enabled, the screen can normally play Presentation content and switch to the Application layer after user interaction. When the interaction ends or the configured timeout expires, it can return to its default mode. The default Application-layer mode can be the Kiosk or one specific web application.

Built-in icon gallery

ScreenSoft includes an extensive built-in icon gallery. Wherever an application or another setting requires an icon, the administrator can either upload a custom icon or select one directly from the ScreenSoft gallery. A separate graphic file therefore does not need to be prepared for common use cases.

Scheduling application publication

Every application can be created and prepared in advance and assigned a publication period on the screen: when it should become available on the selected device and when its publication should end. The principle is similar to campaign scheduling.

An application does not have to appear immediately after it is created. For example, it can be prepared several days before an event, scheduled to become available when the event starts, and automatically stop being shown when the configured publication period ends.

Didn't find what you were looking for?
Contact ScreenSoft support at support@screensoft.org