Admin: a page per playing game with its timeline, and a System page (complete redesign) #161

Closed
opened 2026-11-14 00:31:17 -05:00 by cmoriarty · 1 comment
Owner

The mockup is the Admin redesign canvas: the Playing page for the game being watched, the System page, and the Playing page on a good night and with no stream left. This replaces the nine-section page built in #103 to #110 and #105.

What happens

The owner's words, 2026-11-13: after two redesigns the page is still not intuitive, and "overall it's just noisy and filled with unnecessary nonsense UI elements". His priorities, in order:

  1. While watching a game that skips, freezes or fails, open Admin and at once see that game and everything needed to understand why.
  2. See what the backend is doing, and how it has been doing over time.
  3. Minimal and professional: no extra UI elements, spinners, wheels or giant numbers.

Three more rules came out of the mockup rounds:

  • No paragraph of explanation under a status. The cause is one labelled field, Problem, under the game's name.
  • Swap stays beside Wrong game. It has to work when the app is malfunctioning, so it must not depend on a ready standby, and any link can be picked by hand.
  • No loose phrase of data anywhere. Every value is a labelled field (a small grey label over the value) or a small tag (a state word, a count, a value on a chart mark).

The idea

The frame. The masthead stays. Under it, a sidebar and one page at a time.

  • Sidebar, Playing: one entry per open channel, the game's name with a state tag (Playing, Freezing, Not playing, Warm, Game over).
  • Sidebar, System: Overview, Sites, Log, Settings.
  • /admin opens the game someone is watching; with none, the Overview. Each page has its own address, so a reload stays on it.

A game's page, top to bottom:

  1. The game's name with its state tag. Buttons: Swap, Wrong game, and Stop re-encode only while the stream is re-encoded.

  2. A row of fields: Problem, Sport, On since, Picture, Player, Playback.

  3. Timeline: five rows on one time axis, in the order the video travels. A switch picks the last 10 minutes, the last hour or the whole game.

    • Link: a band per stretch on a link, named by site and stream letter; a dashed band while the app looks for a stream.
    • Source: a bar per wait for the next segment, amber when it reached the wait that fails a stream, with its seconds; errors as tags.
    • Download: a bar per segment's download time, amber when slower than the segment plays.
    • Buffer: the seconds held, with a dashed line at what the channel aims to hold.
    • Player: a bar per wait for the next piece of the playlist, red when long enough to freeze a player; filler as tagged bands.

    Each row starts with its name, a state tag and two fields (for example Pace 0.87× and Longest gap 22 s).

  4. Links: every link of the game with site, stream letter, state tag, last result and when it was checked, and Play on every link that is not playing. Count tags on the heading: links, streams, ready.

  5. Log: the game's events since the tune, as time, event and detail, with the freezes and the filler among them.

Grey means fine. Amber is a cause the app handles. Red is something the viewer saw, or a failure. Blue is what plays now.

System, Overview:

  1. "System" with fields (Version, Up, Last restart) and Pause checks.
  2. Now: a table of the tasks (Task, Doing, Last run, Next), with Running and Idle counts.
  3. Not working: the live followed games without a stream, and the sites that are held back or failing. Each row has a problem tag, one detail, and its actions (Check now, Skip, Try now, New session).
  4. History: five rows on one axis (Games, Stream checks, Sites, Channels, App), over 3 hours, 24 hours or 3 days.

Sites, Log, Settings have no mockup. They follow the same forms:

  • Sites: one table of every site with its state tag, reads, last answer, last 24 hours as cells, and its actions.
  • Log: the event log as a table (time, kind, subject, event), with a window switch, kind filters and paging.
  • Settings: background channels and the head start, as rows of setting, value and control.

What goes

The top bar, the collapsed cards, chips, verdict words, countdown rings, the buffer gauge, the waits strip, the Next panel, the standby search's tally, the Your games tabs, the coverage chart, the draggable history window and the settings pane. What they said moves into the fields, the timeline rows and the tables above. The full list of followed games stays on the Games page.

Data it needs

  • A channel's history. Today the view has the last 3 minutes of waits and the current readings. Each channel keeps, for as long as it is open (at most 6 hours): every wait for a new segment, every download, a sample of the buffer every 2 seconds, every release to the playlist and every upstream error. GET /api/channels/{game_id}/lanes answers a window of it in at most 240 bins, with the counts the fields show.
  • Swap without a ready standby. Today it answers 409. It should drop the link (cooling it, not rejecting it) and find another as a recovery does. The answer says which happened.
  • Play a chosen link. POST /api/channels/{game_id}/play with the link's address. The standby and the backup are swapped in as they are. Any other link is read and verified first. If it does not play, nothing changes and the answer says why.
  • The state and the Problem for each channel, decided by the server from the same facts as today's verdict.
  • A game filter on the event log, for the game's Log.
  • Site reads summed over all sites per half hour, kept 3 days, for the Sites row of the History.

Done when

  • In the unit lane:
    • a channel's history answers a window in bins, with the longest wait, the dry spells and the freezes counted;
    • Swap with no ready standby drops the link and starts a recovery;
    • Play on a standby swaps to it; on another link it reads it first; a link that does not play changes nothing;
    • each channel in the view carries its state and Problem;
    • the event log answers one game's events.
  • In the frontend tests, from fixtures:
    • /admin opens the watched game, and the Overview when nothing is watched;
    • a game's page shows the fields, the five rows with their tags and fields, the links with Play, and the log;
    • Swap, Wrong game and Play post to the server and the page reads again;
    • the Overview shows the tasks, the games and sites not working with their actions, and the five history rows;
    • Sites, Log and Settings render and their controls post;
    • none of the old page's sections is left.
  • By eye: the pages are checked in a browser against the canvas.
The mockup is the [Admin redesign canvas](https://claude.ai/artifact/9jcCKyQ2iAXuaiTzFvTK5w): the Playing page for the game being watched, the System page, and the Playing page on a good night and with no stream left. This replaces the nine-section page built in #103 to #110 and #105. ## What happens The owner's words, 2026-11-13: after two redesigns the page is still not intuitive, and "overall it's just noisy and filled with unnecessary nonsense UI elements". His priorities, in order: 1. While watching a game that skips, freezes or fails, open Admin and at once see that game and everything needed to understand why. 2. See what the backend is doing, and how it has been doing over time. 3. Minimal and professional: no extra UI elements, spinners, wheels or giant numbers. Three more rules came out of the mockup rounds: - No paragraph of explanation under a status. The cause is one labelled field, **Problem**, under the game's name. - **Swap** stays beside **Wrong game**. It has to work when the app is malfunctioning, so it must not depend on a ready standby, and any link can be picked by hand. - No loose phrase of data anywhere. Every value is a labelled field (a small grey label over the value) or a small tag (a state word, a count, a value on a chart mark). ## The idea **The frame.** The masthead stays. Under it, a sidebar and one page at a time. - Sidebar, **Playing**: one entry per open channel, the game's name with a state tag (Playing, Freezing, Not playing, Warm, Game over). - Sidebar, **System**: Overview, Sites, Log, Settings. - `/admin` opens the game someone is watching; with none, the Overview. Each page has its own address, so a reload stays on it. **A game's page**, top to bottom: 1. The game's name with its state tag. Buttons: **Swap**, **Wrong game**, and **Stop re-encode** only while the stream is re-encoded. 2. A row of fields: Problem, Sport, On since, Picture, Player, Playback. 3. **Timeline**: five rows on one time axis, in the order the video travels. A switch picks the last 10 minutes, the last hour or the whole game. - **Link**: a band per stretch on a link, named by site and stream letter; a dashed band while the app looks for a stream. - **Source**: a bar per wait for the next segment, amber when it reached the wait that fails a stream, with its seconds; errors as tags. - **Download**: a bar per segment's download time, amber when slower than the segment plays. - **Buffer**: the seconds held, with a dashed line at what the channel aims to hold. - **Player**: a bar per wait for the next piece of the playlist, red when long enough to freeze a player; filler as tagged bands. Each row starts with its name, a state tag and two fields (for example Pace `0.87×` and Longest gap `22 s`). 4. **Links**: every link of the game with site, stream letter, state tag, last result and when it was checked, and **Play** on every link that is not playing. Count tags on the heading: links, streams, ready. 5. **Log**: the game's events since the tune, as time, event and detail, with the freezes and the filler among them. Grey means fine. Amber is a cause the app handles. Red is something the viewer saw, or a failure. Blue is what plays now. **System, Overview:** 1. "System" with fields (Version, Up, Last restart) and **Pause checks**. 2. **Now**: a table of the tasks (Task, Doing, Last run, Next), with Running and Idle counts. 3. **Not working**: the live followed games without a stream, and the sites that are held back or failing. Each row has a problem tag, one detail, and its actions (Check now, Skip, Try now, New session). 4. **History**: five rows on one axis (Games, Stream checks, Sites, Channels, App), over 3 hours, 24 hours or 3 days. **Sites, Log, Settings** have no mockup. They follow the same forms: - **Sites**: one table of every site with its state tag, reads, last answer, last 24 hours as cells, and its actions. - **Log**: the event log as a table (time, kind, subject, event), with a window switch, kind filters and paging. - **Settings**: background channels and the head start, as rows of setting, value and control. ## What goes The top bar, the collapsed cards, chips, verdict words, countdown rings, the buffer gauge, the waits strip, the Next panel, the standby search's tally, the Your games tabs, the coverage chart, the draggable history window and the settings pane. What they said moves into the fields, the timeline rows and the tables above. The full list of followed games stays on the Games page. ## Data it needs - **A channel's history.** Today the view has the last 3 minutes of waits and the current readings. Each channel keeps, for as long as it is open (at most 6 hours): every wait for a new segment, every download, a sample of the buffer every 2 seconds, every release to the playlist and every upstream error. `GET /api/channels/{game_id}/lanes` answers a window of it in at most 240 bins, with the counts the fields show. - **Swap without a ready standby.** Today it answers 409. It should drop the link (cooling it, not rejecting it) and find another as a recovery does. The answer says which happened. - **Play a chosen link.** `POST /api/channels/{game_id}/play` with the link's address. The standby and the backup are swapped in as they are. Any other link is read and verified first. If it does not play, nothing changes and the answer says why. - **The state and the Problem** for each channel, decided by the server from the same facts as today's verdict. - **A game filter on the event log**, for the game's Log. - **Site reads summed over all sites** per half hour, kept 3 days, for the Sites row of the History. ## Done when - **In the unit lane:** - a channel's history answers a window in bins, with the longest wait, the dry spells and the freezes counted; - Swap with no ready standby drops the link and starts a recovery; - Play on a standby swaps to it; on another link it reads it first; a link that does not play changes nothing; - each channel in the view carries its state and Problem; - the event log answers one game's events. - **In the frontend tests, from fixtures:** - `/admin` opens the watched game, and the Overview when nothing is watched; - a game's page shows the fields, the five rows with their tags and fields, the links with Play, and the log; - Swap, Wrong game and Play post to the server and the page reads again; - the Overview shows the tasks, the games and sites not working with their actions, and the five history rows; - Sites, Log and Settings render and their controls post; - none of the old page's sections is left. - **By eye:** the pages are checked in a browser against the canvas.
Author
Owner

Merged in #162 (merge commit b1a17da) and deployed from main at c926431 on 2026-11-14: the app was up on it at 16:40Z. The OpenSpec change admin-one-game-page is archived in c926431.

Checked on the live app right after the deploy:

  • /admin opens the Overview, and the Overview, Sites, Log and Settings pages draw from real data with no console errors.
  • The site totals were started from the saved sites.json (48 half hours, 2026 reads), so the Sites history row was full at once.
  • /api/events?game= and /api/sites/totals answer; /api/channels/{id}/lanes answers 404 without a channel.
  • The Games and Watchlist pages look as before.

Seen on a live game at 16:58Z (Miami vs. Duke, watched in the web player, playing thetvapp.plus, three minutes after its tune):

  • /admin opened the game's page. The state read Playing and the Problem None.
  • The five timeline rows filled from the channel's history, over the last 10 minutes and over the whole game. The Source row read Uneven and marked two gaps between segments (8.8 s and 7.7 s); the buffer held 10 of 15 s and the Player row read Steady with no freezes.
  • The links table listed the game's 27 links, with Play on every one but the link playing. The game's log showed the tune.
  • The app's log had no warnings, errors or tracebacks since the deploy (1,398 lines).

Not pressed on a real channel yet: Swap, Play and Wrong game.

Merged in #162 (merge commit b1a17da) and deployed from `main` at c926431 on 2026-11-14: the app was up on it at 16:40Z. The OpenSpec change `admin-one-game-page` is archived in c926431. Checked on the live app right after the deploy: - `/admin` opens the Overview, and the Overview, Sites, Log and Settings pages draw from real data with no console errors. - The site totals were started from the saved `sites.json` (48 half hours, 2026 reads), so the Sites history row was full at once. - `/api/events?game=` and `/api/sites/totals` answer; `/api/channels/{id}/lanes` answers 404 without a channel. - The Games and Watchlist pages look as before. Seen on a live game at 16:58Z (Miami vs. Duke, watched in the web player, playing thetvapp.plus, three minutes after its tune): - `/admin` opened the game's page. The state read Playing and the Problem None. - The five timeline rows filled from the channel's history, over the last 10 minutes and over the whole game. The Source row read Uneven and marked two gaps between segments (8.8 s and 7.7 s); the buffer held 10 of 15 s and the Player row read Steady with no freezes. - The links table listed the game's 27 links, with Play on every one but the link playing. The game's log showed the tune. - The app's log had no warnings, errors or tracebacks since the deploy (1,398 lines). Not pressed on a real channel yet: Swap, Play and Wrong game.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/sports-breaker#161
No description provided.