Branding and Whitelabel
Whitelabel branding for deployment apps is a paid DevSpace add-on. If it is not enabled for your company, apps are built exactly as before. Contact your signageOS account manager to have it enabled.
By default, every app generated by Smart Builder is installed on the device under the signageOS name and icon. With whitelabel branding you replace both, so the app in the device launcher carries your application title and your logo — while signageOS keeps maintaining the Core App underneath.
This is the device-side counterpart of CloudControl Whitelabel, which brands the management portal.
devSpace · Availability: DevSpaceWhat gets branded
| What | Branded |
|---|---|
| Application name in the device launcher / home menu | Yes |
| Application icon in the device launcher / home menu | Yes |
| Application name shown inside the app | Yes |
| Application / package identifier | No — it stays a signageOS identifier |
| Provisioning URLs and download links | No |
The application identifier never changes. That is intentional — it is what allows an already installed app to be upgraded in place instead of being installed side by side as a second app.
Supported platforms
| Platform | Supported | Notes |
|---|---|---|
| Samsung Tizen / SSSP | Yes | Home-menu label, icon, and in-app name |
| LG webOS | Yes | Launcher title and icon |
| Android | Yes | Launcher label and icon |
| Windows, Linux, BrightSign, ChromeOS | No | Apps are built unbranded |
Platforms that are not supported are simply built without branding — you can select them in the same build request.
Prerequisites
- Whitelabel branding is enabled for your company
- You have created your Applet and uploaded it to your DevSpace account
- You have a square logo image, at least 512×512 pixels (optional — see Logo)
How to build a branded app
- Go to the Smart Builder section of Box and click Generate deployment app
- Select your Applet, its version, the CoreApp base, and toggle the native apps you want to build
- In the Branding section, tick the branding checkbox, then upload a Logo and set the Application title, both described below
- Press Generate and wait for the build to finish
The branded app is produced for every supported platform in the same build request.
Logo
Upload a square PNG or JPEG, at least 512×512 pixels. signageOS downscales the image to the icon size each platform expects — 512×512 for Tizen and Android, 200×200 for webOS — and never upscales it, so one upload covers every platform.
If you do not upload anything, the icon of the selected Applet is used instead. Applet icons uploaded from a square source of at least 512×512 pixels are stored in all the sizes branding needs and look sharp on every platform; older or smaller Applet icons are only stored at 50×50 and will look blurry in the device launcher. When neither a logo nor an Applet icon is available, the app keeps the default signageOS icon.
Upload the logo explicitly whenever you care about how the icon looks on the device. It is the only way to be sure the launcher gets a full-resolution image.
Application title
The Application title is the name shown to users on the device. It is pre-filled with your company name and you can change it before building.
On Samsung Tizen and SSSP devices, the home-menu label is derived from a filename-safe version of the title: accents are stripped and spaces and other special characters are removed. A title of Acme Retail TV shows on the Samsung home menu as AcmeRetailTV, while the name inside the app keeps the full title. Titles written entirely in non-Latin characters cannot be used as a home-menu label at all, and the app keeps its default label.
Keep Samsung titles short and Latin-only if the home-menu label matters to you.
After the build
The branded name and icon are part of the installed package, so they apply from the moment the app is installed:
- New devices — provision them from the branded build as usual, following the provisioning guides.
- Devices that already run an unbranded app — upgrading in place updates the app, but some device launchers keep showing the previously registered label and icon until the app is reinstalled. Perform a clean install when the branding must be visible immediately.
Branding is stored per build, not per company — every new build request has its own Branding section, so a change of title or logo takes effect with the next generated app.