Android TV vs. AOSP white paper
Implications on Total Cost of Ownership and Content Security

Over the last decade, the Android operating system has become one of the most widely used platforms  across different consumer devices. While Android has seen wide success on Smartphones  and tablets, its growth is not limited to those platforms.

Five key drivers that attract pay-TV providers to Android set-top-box (STB) propositions are giving subscribers access to apps and services, increasing end-user engagement, exploring new monetization avenues, reducing the time to market for new STBs and decreasing churn by keeping subscribers on HDMI1 – TV input which is controlled by the operator Device.

To gain a more in-depth perspective of the commercial benefits it is essential to understand the different variants of Android STBs that can be deployed in a pay-TV operation. These include:

  1. Android TV STB
  2. AOSP-based STB compliant with Android CDD
  3. AOSP-based STB not compliant with CDD (a.k.a. AOSP Fork)

This paper will explore the pros and cons of each variant of Android in the context of STB Development  projects for pay-TV operators. Furthermore, the paper will look at the difference in effort and complexity for  Android TV and AOSP (Android Open Source Project) based on compliance with CDD, providing insight into the commercial impact of each variant for an operator and the overall benefits vs. trade-offs.