STREAMING UX CASE STUDY

Designing multiscreen streaming experiences across markets

At 3SS, I worked on large-scale TV and streaming products for operators across Europe and Latin America, designing experiences that had to work across Smart TV, Apple TV, mobile, web, Android TV, and set-top box environments.

  • Streaming UX
  • Multiscreen Design
  • TV Apps
  • Product Design
  • Design Systems

A streaming product built for different screens, clients, and markets

At 3SS, I worked on TV and streaming products for operators including Allente, Elisa Estonia, and TCC Uruguay. While each client had its own market, content strategy, platform requirements, and business priorities, the core design challenge was similar: create a high-quality entertainment experience that could scale across devices and still feel tailored to each operator.

This meant designing for more than one screen size. A streaming experience behaves differently on a remote-controlled TV interface, a mobile app, a web platform, and a set-top box. The work required balancing platform-specific interaction patterns, content discovery, client requirements, and long-term product consistency.

Keeping users engaged in a fragmented streaming landscape

TV operators compete in an environment where users have more content choices than ever. The challenge was to design experiences that made content easier to discover, easier to continue watching, and easier to trust as a daily entertainment destination.

Unlike a single-platform product, these experiences had to work across different devices, input methods, technical constraints, and client ecosystems. A pattern that works well on mobile does not automatically translate to a 10-foot TV interface controlled with a remote. The design needed to feel consistent, but not identical, across platforms.

The challenge was to create a product experience that could scale across screens without becoming generic.

Designing inside real platform and client constraints

This was not a research-heavy case study. Much of the work happened inside an active product environment, shaped by client requirements, platform limitations, technical feasibility, design-system constraints, and ongoing sprint delivery.

The value of the design work came from translating complex requirements into clear flows, scalable interface patterns, and production-ready solutions that could support multiple operators without losing the quality expected from a modern streaming product.

  1. 01

    Different platforms required different interaction models, from touch-based mobile flows to remote-controlled TV navigation.

  2. 02

    Different clients needed the product to reflect their brand, content strategy, and market expectations.

  3. 03

    The product had to support large content libraries while keeping discovery and navigation simple.

  4. 04

    Design decisions had to remain feasible for engineering teams and reusable across multiple implementations.

Creating consistency without forcing every platform to behave the same

The design direction focused on creating a shared product language that could flex across clients and devices. Instead of designing isolated screens, I worked on reusable flows and interface patterns that could support different entertainment contexts: browsing, search, content details, playback entry points, account areas, settings, and platform-specific navigation.

Constraint

Multiple screens and input methods

Design decision

Adapt interaction patterns to each platform while keeping the product experience recognisable

Constraint

Large content libraries

Design decision

Prioritise clear navigation, content hierarchy, and continuation flows

Constraint

Different client brands and markets

Design decision

Use a scalable design foundation that could support client-specific customisation

Constraint

Ongoing delivery across product teams

Design decision

Create clear flows, prototypes, and design reviews to reduce ambiguity before development

A multiscreen streaming experience designed for scale

The work covered multiple parts of the streaming experience, from content discovery and navigation to details, playback entry points, account areas, and platform-specific flows. The goal was to create interfaces that felt simple for users while staying flexible enough for different operators and screen types.

Content discovery across screens

I designed browsing and discovery experiences that helped users move through large content libraries, continue watching, and find relevant entertainment across TV, mobile, and web environments.

Smart TV streaming interface showing featured content, navigation sidebar, and content rails with remote-friendly focus states

Platform-specific interaction patterns

I adapted product flows for different interaction models, from remote-controlled TV navigation to mobile touch interactions. The goal was to keep the experience consistent while respecting how users behave on each platform.

Elisa tablet streaming app showing video playback and EPG grid with touch-first navigation and selected program focus state

Reusable design foundations

I worked with product and engineering teams to create scalable UI patterns, prototypes, and design reviews that helped align stakeholders and support delivery across multiple client implementations.

Live products across multiple platforms

The work contributed to streaming products that launched and continued evolving across multiple platforms. These products were not static handoffs; they were improved sprint by sprint, shaped by client needs, product priorities, and ongoing quality reviews.

3

TV & Streaming providers

4M+

Customers

7+

Platform types

What this project demonstrates

This case study demonstrates my ability to design inside complex product environments where the challenge is not only the interface, but the system around it: clients, platforms, devices, technical constraints, content models, and delivery teams.

The work taught me how to think beyond a single screen and design for product ecosystems. Streaming products need to feel effortless, but the design decisions behind them are often shaped by platform behaviour, remote-control navigation, content strategy, and implementation trade-offs.