Why does this matter?
Imagine Netflix has millions of devices — smart TVs, phones, gaming consoles, streaming sticks. Each device has different hardware:
| Device | RAM | Display | Audio |
|---|---|---|---|
| Old Smart TV | 1GB | HD only | Stereo |
| New Streaming Stick | 2GB | 4K | Surround Sound |
| Budget Phone | 512MB | 720p | Basic |
❗ Key Insight: You cannot push a 4K feature to a device that only supports HD. Doing so breaks user experience.
Therefore: Netflix needs a system to know what each device can do.
Netflix builds a data model that captures each device's capabilities, including:
Think of it like a detailed profile card for every device model.
Purpose: Track the latest state of each individual device
How it works:
Example data structure:
{
"Screen Height": ["720"],
"Screen Width": ["1280"],
"Video Profiles": [
"playready", ← HD capability
"hevc" ← UHD/4K capability
]
}
How to read this:
This specific device has a 720p screen (1280×720) and supports both HD and UHD video profiles
Purpose: Understand capability distribution across many devices
How it works:
Example:
{
"Video Profiles": {
"playready": "100%", ← ALL devices support HD
"hevc": "20%" ← Only 1 in 5 devices support UHD
}
}
Real-world interpretation:
Out of all active streaming sticks, every device can stream HD content, but only 20% can stream in 4K Ultra HD
Cumulative Table Histogram Table
───────────────── ─────────────────
"What can THIS "What % of ALL
device do?" devices can do X?"
↓ ↓
Per-device Aggregate-level
detail distribution
└──────────┬───────────────┘
↓
Analytics Products
(Feature decisions)
Using this data, Netflix can answer questions like:
| Question | Data Used |
|---|---|
| Can we enable 4K on this device model? | Cumulative Table |
| What % of users can access Spatial Audio? | Histogram Table |
| Is it worth building Cloud Gaming for older TVs? | Histogram Table |
| Which devices need a software update to support new UI? | Both Tables |
Example Decision:
If only 20% of devices support HEVC (UHD), Netflix knows that rolling out a 4K-only feature would exclude 80% of users — a data-driven reason to maintain HD fallback support
| Concept | Key Takeaway |
|---|---|
| Why model capabilities | Devices differ; wrong features = bad experience |
| Cumulative Table | Latest snapshot of individual device capabilities |
| Histogram Table | Distribution of capabilities across active devices (28-day window) |
| JSON structure | Capabilities stored as key-value pairs for flexibility |
| Business value | Enables smarter, faster, data-driven feature rollout decisions |
💡 Core Principle: Data about what devices can do enables Netflix to decide what features to build and deploy — maximizing both innovation speed and user experience quality.