ANODA Discuss your product

Media & Entertainment Product Design

Design the products people watch, listen to and take part in — how they find something, how it plays on every screen, and the tools your team uses to schedule, moderate and run it live.

Discuss your product Explore our work
A steel robotic arm on a wheeled base presses an orange play tile into the centre of a blank white ceramic screen.
For streaming and live teams
TV, music, events, digital art
TV, web and mobile
Remote, thumb and mouse
Five published media cases
Streaming, TV guide, live events, art
Design first
Development scoped separately

In short

Content people find, play and come back to, and the tools your team runs it with.

What's included

  • Content discovery
  • Playback and live
  • TV guides and schedules
  • Moderation and production
  • Admin and content tools
  • TV, web and mobile

Answers you'll have before development

  • What does a viewer see first, and what next?
  • How does it work with a remote, a thumb and a mouse?
  • What does the team need while an event is live?

Where it stops

B2C & Consumer Products

Consumer products in any category.

Media & Entertainment Product Design

Content, playback and the teams behind them.

Not included

  • Development, streaming infrastructure or licensing
  • Audience, watch-time or revenue figures

The audience's side and the team's

What people watch and do, and what the people running it need.

Discuss your product
  • A thin steel rack of three shelves holding rows of white ceramic tiles like covers, one tile in graphite.

    Content and navigation model

    Catalogues, categories, search and what each audience sees first.
  • A white ceramic TV screen on thin steel legs carved with a play symbol, a small graphite remote in front.

    Playback, live and schedule screens

    Players, live events, guides and reminders, for each screen size.
  • A white ceramic control console with a row of steel-slotted faders and square buttons, one knob in graphite.

    Team and moderation tools

    Content queues, approvals and live controls for the people running it.
  • A steel-rimmed white ceramic tray of small component pieces — buttons, toggles and sliders — some of them in graphite.

    Design system and handoff

    Components for TV, web and mobile, in light and dark.

You receive

  • A screen map for every platform
  • Flows with every state
  • UI and a clickable prototype

Designed for the couch, the phone and the control room.

People watch on a TV across the room, a phone on the move and a laptop at a desk, while a team keeps content flowing behind them. We draw every moment for the screen it happens on.

Every screen is designed for

  • New viewer, no history yet
  • Buffering or a weak signal
  • Offline on the move
  • Not available in this region
  • Live event about to start
  • Schedule changed
  • Content waiting for moderation
  • Driven by a TV remote
  • Kids or larger-text mode

Right for products people watch on several screens

It fits when content is the product, and people meet it on more than one screen.

  • Content is the product

    People come to watch, listen or take part, and leave when they can't find something.

  • More than one screen

    The same catalogue has to work on a TV, a phone and a desktop.

  • A team runs it live

    Editors, moderators or producers schedule, approve and publish while people watch.

  • The feeds and rights are set

    Catalogue data, schedules and regional rights are known, so the design can follow them.

A different starting point

Let's design what people watch next

Tell us what your audience watches, where they watch it and who runs it behind the scenes. We'll suggest a starting service and what it would cover on each screen.

Discuss your product Explore our work

Scope, access and who does what

Your product's stage picks the service, and that service's proposal holds the terms for TV, web and mobile alike.

Scope
Per service fixed or phased, set in the proposal
Timeline
Agreed after scope, access and dependencies
Discuss your product

  1. You provide

    The product
    Test accounts for the live apps or staging, on every platform you ship.
    The content
    How the catalogue, schedules and live events are structured, and where the data comes from.
    Evidence
    What people search for and can't find, where they drop, and what support hears.
    Engineering
    The team, the player and streaming stack, and what each TV platform allows.

  2. Who does what

    ANODA
    Models the catalogue and who watches it, designs every screen and state per platform, and writes what engineers need to build each one.
    Your team
    Owns the content, rights and data feeds, reviews every round, and builds and releases the apps. Licensing, age ratings and legal review are your call.

  3. Boundaries

    Outside media design
    Development, streaming and player infrastructure, content licensing, and legal or age-rating review.
    After the design
    Your engineering team or an agency builds the apps. Should you want us to build them, that is a separate engagement.

In the client's words

The design direction gave the TV guide a more consistent way to present programmes and channel information. We appreciated the attention to browsing and navigation, so the guide could be reviewed as one connected experience.

Tomas Mazowski Co-Founder, TV24 Group Read the TV24 case

Related services

Product types

Industries

Where do viewers lose the thread?

Tell us what the product plays, on which screens, and who runs it behind the scenes.

What do you need? *
Project budget (USD) *

What is your product, who uses it, and what would you like us to do?

    Within 15 minutes, we’ll reply with initial feedback and follow-up questions.

    Read more about apps people come back to

    All articles

    Media & Entertainment Product Design: common questions

    What separates a media app design team that has shipped players from one that only draws thumbnails?

    Pick people who have built your kind of product before — a streaming app, a TV guide and a live-event tool are different jobs. Ask to see the unhappy states: a stream that buffers, a show that is not available in a region, a schedule that changed, content waiting for moderation. And check which screens they have designed for, a TV and its remote included, and who from their studio would be on yours.

    What does media UX design cover, and why do two projects rarely cost the same?

    A content and navigation model, playback, live and schedule screens, the team's moderation and admin tools, the states that connect them, a design system per platform, and a working prototype of the UI. The price moves with the number of platforms — TV, web and mobile — the size and structure of the catalogue, the audiences and roles, and whether viewers already use the product. The first service's proposal carries a scope written for your catalogue, and the schedule is agreed when we know what access and the player's dependencies involve.

    Who are you designing for — the viewers and fans, or the team running the channel?

    Viewers, listeners and fans; subscribers and families, including children; artists and creators; and the teams behind the product — editors, producers, moderators, venue staff and admins. The workflows are browsing and search, playing and following live events, schedules and reminders, saving and personal lists, sending content to another screen, and the team's queues for publishing, moderating and displaying content.

    Which service should a streaming, TV or live-event product start with?

    A new product begins in UI/UX & Product Design; one viewers already use that has outgrown its interface moves to UI Redesign. Streaming app design usually runs through Mobile App Design and Web App Design, with the TV interface designed alongside. Dashboard Design covers the numbers producers and advertisers watch, and Design Systems keeps TV, web and mobile consistent. Building the apps is a separate engagement with its own scope.

    Rights, age ratings and accessibility: does your design certify any of them?

    Your team owns content rights, regional availability, age ratings and legal review; we design how each one appears to people. That covers what a viewer sees when something is not available where they are, how kids' modes and parental controls behave, and larger text, contrast and remote-only navigation. We design for accessibility and check it in the design, but that check certifies nothing: legal, regulatory and accessibility sign-off stays with you.

    What will you need from our product, content and engineering people?

    Test accounts for the live apps or staging on every platform; how the catalogue, schedules and live events are structured and where the data comes from; search, drop-off or support data if you have it; a person who can settle product questions; and engineers who can tell us what the player, the streaming stack and each TV platform will and will not do.

    What have you designed for viewers, listeners and fans?

    Vixi Suite, a live-event fan-engagement platform — 200+ screens designed; TV24, a TV guide for phones and tablets — 79+ screens, for line-ups of more than 18,000 channels; Blackdove, a digital art platform — 300+ unique screens; HyperSign LifeVue, a hospital TV interface with 3 interface modes; ZooPlus, a responsive live animal-streaming platform for viewers, Zoo Admins and a Super Admin; and Wildcast, the interface design of a podcast advertising marketplace with 3 portals redesigned.

    Will a redesign work with the player and TV platforms we already have?

    Yes. Most entertainment app design starts from a product people already use, a player that is already chosen and a catalogue that already exists. Each screen respects what the player and each TV platform allow; we work in your design files and system, together with your own designers and engineers, and leave you every file.