NMOS Router — Diana Kuzachenko
← All cases

Enterprise mediaNMOSMVP prototype

Media stream router for IP broadcast

Aligned the UX model before costly backend integration — the team got a prototype and specs for effort estimates and roadmap.

Routing Matrix — main MVP screen from the clickable prototype
Open prototype

Situation

The module helps professional users manage media routing in IP broadcast: link Sender → Receiver, check compatibility, use presets, and review action history.

The domain is dense — NMOS and SMPTE ST 2110 standards, high cost of on-air mistakes, several professional roles. Before backend integration the team needed a unified UX model, not a loose set of screens.

Task

Without a shared UX model it was hard to estimate backend scope and development priorities.

High cost of errorWrong routing can break live broadcast workflows — critical actions need checks and explicit feedback.
Complex domainSender, Receiver, NMOS, ST 2110, RDS (Registration and Discovery System) status, compatibility — technical entities must be clear to different roles.
Several professional rolesOperators need fast overview and actions; engineers need technical foundation; admins need journal and incident control.
Expensive backend integrationA wrong UX model could force costly rework after development started.
Fragmented product modelMatrix, Devices, presets, and journal risked evolving as disconnected screens without a shared action language.

Align the MVP module UX model before development: define key surfaces, agree on critical action language, show links between Matrix, Devices, Salvo, and Journal, and give the team a prototype and specs for backend scope estimation.

Action

Mapped the domain with product and engineering, ran competitive analysis, designed the information architecture, and built a clickable HTML prototype with text specs — all before backend integration started.

  1. Mapped the domain with product and engineers: roles, scenarios, Sender / Receiver entities, critical Take / Release / Lock / Schedule actions.
  2. Competitive analysis: Nevion VideoIPath, EVS Cerebrum, Haivision StreamHub — matrix density, resource tree, presets, monitoring, audit patterns.
  3. Designed IA: Routing Matrix as default entry, Devices as the authoritative device registry, Salvo as preset layer, Journal as audit layer.
  4. Built clickable HTML/CSS/JS prototype with mock data and text specs for product review and backend estimation.

Key trade-offs

  • Backend integration was costly and risky — the UX model had to be aligned before development.
  • Journal as audit layer: with high error cost, history and consequences of critical actions are mandatory.

MVP product model

Routing Matrix — main operational surface

The matrix is the primary screen for Sender × Receiver links: filters, selection, Take / Release / Lock / Schedule, compatibility check, explicit statuses.

Routing Matrix from the MVP prototype: Sender × Receiver, filters, Take / Lock / Schedule

Devices — authoritative registry

Technical foundation: NMOS tree, device cards, Sender / Receiver parameters, manual add, scan. RDS (Registration and Discovery System) status shows whether the NMOS registry server is running and whether Registration API (for devices) and Query API (for controllers) are available.

Devices tree / Sender–Receiver card / RDS status

Salvo — preset layer

Prepared routing scenarios: preset list, editor, immediate or scheduled run, live status.

Salvo presets: create / edit / run / schedule

Journal — audit layer

History of Take / Release / Lock / Schedule, execution status, live events, link to user, time, and affected route.

Journal audit log / event details

Critical operational flow

  1. User selects Sender and Receiver.
  2. System checks compatibility.
  3. User chooses Take, Release, Lock, or Schedule.
  4. System shows explicit feedback and status.
  5. Action is logged in Journal.

Result

The team got an aligned UX vision for the enterprise module before costly backend integration — prototype and specs used for product review, effort estimates, and roadmap prioritization.

4Key surfaces

Routing Matrix, Devices, Salvo, Journal — aligned before integration.

4Critical actions

Take, Release, Lock, Schedule — documented with compatibility check.

3Roles mapped

Engineer, operator, admin — scenarios fixed in specs.

4Prototype screens

Clickable mocks with mock data: matrix, devices, Salvo, journal.

Public prototype & AI

Case uses mock data only — no client or production infrastructure. The clickable MVP prototype is linked below and can be explored freely. AI accelerated research and draft prototyping; final UX model, product decisions, and copy are by the designer.

Open prototype Next case Get in touch