One Product, Many Surfaces: Web, Mobile, and Smart TV Around a Shared Core

A product that expands from web to mobile and television can become three disconnected products surprisingly quickly. The browser team adds one permission rule, the mobile app stores a different preference, and the TV client invents its own recovery behaviour. Customers experience the inconsistency, while the operations team has to explain why the same account behaves differently on every screen.

Keep policy and product state in one operating core

Identity, plans, roles, device registration, content metadata, entitlements, and administrative actions should come from a shared backend. Each client can cache carefully and adapt presentation, but it should not quietly redefine business rules. Stable APIs and explicit versioning make product changes predictable across devices.

• Keep authorization and subscription rules server-owned
• Use one source of truth for account and device state
• Design refresh, retry, and session recovery before launch
• Version APIs when clients cannot update together
• Record important administrative actions for support and audit

Share product language, not identical layouts

Consistency does not mean stretching one interface across every screen. Mobile users expect touch, interruption recovery, and compact tasks. Television users need predictable focus, large targets, and a clear back-button hierarchy. Desktop operators may need dense tables and bulk actions. A design system should share status language, spacing principles, and interaction rules while allowing each surface to solve its own input problem.

Treat failure paths as product features

Multi-platform systems usually fail at boundaries: stale sessions, interrupted requests, provider timeouts, unsupported media, and partial synchronization. Bounded retries, idempotent actions, safe caches, and understandable recovery states create more value than another decorative screen. The system should always tell the user what happened and what they can do next.

The goal is not one interface stretched across devices. The goal is one product expressed correctly on every device.