2026-04-01 - Platform Build Split: Tizen, webOS & BrightSign
Effective Date: January 2027
Starting January 2027, signageOS will enforce platform build separation for Tizen, webOS, and BrightSign. Today, no action is required - your existing deployments continue to work as before. This announcement provides advance notice so you can prepare your deployment workflows ahead of the change.
What is Changing
Hardware vendors (Samsung, LG, BrightSign) are introducing breaking changes and API incompatibilities between older OS releases and their latest platform versions. To deliver the greatest features, capabilities, and security on modern hardware while maintaining full support for existing devices, signageOS is splitting three platforms into legacy and modern build targets.
Until January 2027, CoreApps for these platforms will continue to run in compatibility mode - a single build that works across both legacy and modern OS versions. Starting with the next major CoreApp release in January 2027, compatibility mode will end and the split becomes permanent. Each of the affected platforms will then require you to select the correct build target based on the device's OS version.
Build Target Reference
Smart Builder and DevSpace already display these as separate build targets. After January 2027, they will produce distinct application packages.
| Platform | Legacy Build Target | Covered OS Versions | Modern Build Target | Covered OS Versions |
|---|---|---|---|---|
| Samsung Tizen | Tizen | Tizen 2.4, 3.0, 4.0, 5.0, 6.5 | Tizen TEP | Tizen 6.5, 7.0, 8.0 |
| LG webOS | webOS | webOS 1.0, 2.0, 3.0, 3.2, 4.0, 4.1, 6.0 | webOS IDCap | webOS 6.0, 8.0, 9.0 |
| BrightSign | BrightSign | BrightSign OS 8 (gen 3, 4) | BrightSign 9 | BrightSign OS 9 (gen 4, 5, 6) |
For the full list of all supported build targets, see Build Targets.
Why This Change
- Vendor-driven incompatibility: Newer platform OS versions ship with updated APIs, security requirements, and runtime environments that are incompatible with older firmware
- Security: Modern OS releases require updated cryptographic standards, certificate handling, and network protocols that cannot be backported to legacy OS
- Performance & features: New hardware capabilities (hardware decoding, improved rendering engines, expanded storage APIs) can only be leveraged with platform-specific builds
- Stability for legacy devices: Maintaining a single build forced compromises - either limiting modern features or risking regressions on older devices. Separate builds eliminate this tradeoff
Timeline
| When | What | Action Required |
|---|---|---|
| Now | Smart Builder and DevSpace already show separate build targets. CoreApps run in compatibility mode - a single build covers both legacy and modern OS versions | None - existing single-target builds continue to work |
| January 2027 | Compatibility mode ends. Major CoreApp version released for each platform; builds are permanently split | Select the correct build target per device OS version |
There are no intermediate milestones. Until January 2027, CoreApps operate in compatibility mode. The January 2027 major release is the hard split point - after this date, legacy and modern builds will diverge permanently.
What This Means For You
CloudControl
- No manual action required - signageOS CloudControl handles CoreApp updates to a correct version automatically under the hood
- The correct flavor of the CoreApp will be delivered to each device based on its platform version
- You remain in control of when updates are deployed, as always
DevSpace
Smart Builder Users
- Smart Builder already displays the legacy and modern build targets separately
- After January 2027, ensure you select the correct target matching your device fleet's OS version
- If you operate a mixed fleet (e.g., Tizen 4.0 and Tizen 7.0 devices), you will need to build for both targets and deploy the correct package to each device group
JS API Users
- Build your applet for all required flavors (e.g., both
tizenandtizen-tepif you have mixed devices) - When deploying via the JS API, pass the correct App URL corresponding to the target platform version
- Review the CoreApp Versions and Release Policy for platform endpoint URLs
Support Commitment
Legacy build targets remain first-class citizens of the signageOS platform. There is no deprecation, no sunset date, and no reduced SLA. Older OS releases will continue to receive production CoreApp updates, bug fixes, and security patches on the same schedule and with the same quality guarantees as modern targets.
Pricing & DevSpace Plans
Each build target counts as one target against your DevSpace plan quota. If you currently build for a single "Tizen" target and need to support both legacy and modern devices after the split, this will count as two build targets.
Review your DevSpace plan configuration and CloudControl and DevSpace Plans to ensure your quota accommodates the additional targets if applicable.
Before January 2027, review your deployment guides, educate your team and end customers, and verify which OS versions are running across your device fleet. Use the build target reference table above to determine which targets you will need after the split.
Frequently Asked Questions
Will my existing deployments break? No. Existing deployments will continue to function. The split only takes effect with the January 2027 major CoreApp release. Current builds remain fully operational prior and after this date.
Do I need to redeploy my devices? No. CoreApp updates to a newer versions are handled automatically. Currenly deployed versions are not anyhow impacted. There is no force-update needed.
Are legacy platforms being deprecated? No. Legacy build targets (Tizen, webOS, BrightSign) will continue to receive full support - production releases, security patches, and bug fixes.
What if I have a mixed fleet with both old and new devices? Build for both the legacy and modern targets. Deploy the correct flavor to each device group based on OS version. Smart Builder and Box already support this workflow.
How do I know which target my device needs? Check the device's OS version (visible in Box under device details) and compare it against the build target reference table above.
Will pricing change? Each build target counts as one target in your DevSpace plan. If you now need two targets where you previously needed one, your usage increases accordingly. Review your plan to ensure sufficient quota.
For questions or concerns, reach out to support team or your dedicated account manager.