How ZDF manages the new complexity of TV distribution with one codebase

Customer challenges and needs

ZDF managed a growing number of environments. Samsung Tizen, LG WebOS, Android TV, Fire TV, HbbTV and other platforms each required dedicated maintenance. Features and fixes had to be implemented several times. QA multiplied with every additional target.

This model limited speed and scale. It made consistent UX difficult and created operational overhead for editorial, engineering and QA teams. Even small updates required separate reviews and certifications. The complexity also undermined ZDF’s public service mandate: stable, accessible and reliable distribution on every relevant device in Germany.

The table below highlights the most relevant connected TV platforms where the ZDF app is available, ranked by actual usage. ZDF operates its app on a diverse set of CTV platforms, covering both modern streaming devices and older TV environments with significant reach. 

HbbTV and Amazon Fire TV lead the list as the main entry points for ZDF content. They are followed by Android TV, Samsung Tizen and older HbbTV versions. LG WebOS and Sky sit in the middle range. Apple TV, Magenta TV legacy systems and Panasonic SmartHome still see meaningful usage. Even older Samsung devices and newer platforms like VIDAA generate steady traffic.

Our solution

ZDF chose a different approach. Together with Qvest, the broadcaster moved all applications into one modular frontend framework. The architecture uses a layered setup that lets teams write once, adapt where needed, and deploy across many environments.

Core Logic Layer
The core contains everything that defines product behavior. Playback logic, routing, state management, analytics and data handling run as a shared TypeScript base. It acts as the single source of truth and remains independent of device runtimes.

Adapter Layer
Platform differences are handled through small adapters for Tizen, WebOS, Android TV, HbbTV, Fire TV and more. Rendering, input models, DRM and system APIs sit inside these modules. Adding a new environment requires only a new adapter, not an entirely new application.

UI Component Library
A consistent design system provides a unified visual experience. Components adapt automatically to performance and certification requirements of each platform.

Unified tooling and rollout
ZDF now uses a single CI/CD pipeline for all builds. Automated tests validate the shared core and only small variations per platform. Monitoring and error tracking feed into one dashboard. This reduces risk, simplifies operations and accelerates the release process.

The frontend framework is the foundation for these ZDF applications across more than 25 connected TV platforms:

• Relaunch of the ZDF streaming portal

• Launch of the new TIVI

• Relaunch of ZDFheute

All three projects used the same framework and benefited from faster delivery and consistent behavior.

Result

The new setup changed how ZDF develops, operates and maintains its digital products. Release cycles became much faster. Updates that once required several branches now ship from a single commit. QA and maintenance effort dropped significantly. 

The unified architecture also reduced risks related to fragmentation. New devices and standards no longer create exponential overhead. Each additional platform becomes a manageable adapter task. 

ZDF now provides a consistent and reliable user experience across all major connected TV environments, from HbbTV and Fire TV to Android TV and Apple TV. The framework was shortlisted for the HbbTV Awards 2025 in the category “Best Tool or Product for HbbTV Service Development or Delivery”.

Conclusion

For ZDF, this was more than a technical shift. It created a sustainable model for reach and stability across a fast-changing device landscape. With one shared codebase, ZDF scales without multiplying cost or complexity. It strengthens product quality, reliability and long-term flexibility for public service media.