R1 — Device-role chip · DM Track Timer Documentation

SETUP

Same fixture, just opening a different window

The R1 chip is purely a UI surface — no extra fixture state needed beyond what the M1/M2 walkthroughs already use. The chip's content is derived from coordinator.deviceRole (the Mac's static role is Operator; iPad's is Primary) plus the capabilities cache (which advertises silently in the background regardless of whether the chip is visible).

The DM Track Archive window just after launch.

Mac archive just after launch.

STEP 1

Open Live Meet

The role chip lives in the Live Meet window's header (the iPad and iPhone surface them too — same chip code, same styling, different host). On the Mac, Cmd+Shift+M opens Live Meet, or pick it from the Window menu — below, with the entry highlighted in blue so you can see what to click.

Window menu open with Live Meet highlighted in blue, showing its Cmd+Shift+M shortcut.

Window menu · Live Meet highlighted · ⌘⇧M shown next to the entry.

STEP 2

Spot the chip in the header

The Live Meet window opens onto the Sample Invitational meet. Look at the top row of the meet header, right of the meet title: the chip reads Operator with a gray "you're just looking" tint (the Mac doesn't host the timing bus today — that's the iPad's role). Next to it: the Cloud Sync chip, then the Studio / Track Map / Start Sources buttons.

Live Meet window with the Operator role chip visible in the header next to the Cloud Sync chip.

Live Meet header, left to right: meet title · Operator role chip · Cloud Sync chip · Studio · Track Map · Start Sources.

Color language across roles: Primary gets the accent crown tint (you're boss-of-the-meet), Standby is orange (you're ready to take over if Primary drops), Satellite is blue (you're contributing — camera feeds, etc.), Operator is gray (informational only). The iPad chip currently shows Primary; the iPhone shows Satellite when it's running in Satellite mode.

STEP 3

Hover the chip

The chip is a Button when an onTap handler is provided, which Live Meet supplies — readers see the button-bordered state on hover. Hovering before the click also surfaces the tooltip via SwiftUI's .help(...) modifier: "Mac's role · Operator (informational only in R1)".

The Operator chip hovered in the Live Meet header, showing the bordered button state.

Chip hovered. The bordered-button styling makes it clear the chip is tappable.

STEP 4

The capabilities popover

Clicking the chip anchors a popover below it listing every connected device the coordinator has seen capability data for. Each row: device name + role icon + capability pills (audio start · BLE start · Camera · Archive) + last-seen timestamp.

Capabilities popover anchored below the role chip showing Joshua's MacBook Pro Archive with audio start / BLE start / Camera / ARCHIVE pills.

Capabilities popover for the Mac. R2's capability advertisement runs whether or not the chip is visible; the popover is just the operator's window into that cache.

Why this exists: at a meet you want to spot at-a-glance which devices are alive + what they can do. A coach borrowing a parent's iPhone for a finish-line camera should be able to confirm it's actually advertising before the gun goes off. The chip + popover collapse "device topology" into one toolbar element.

UNDER THE HOOD

What R1 covers and what's coming

R1 — visibility (this walkthrough). The chip + the basic capabilities popover. Roles are computed from today's static architecture (iPad = Primary; Mac = Operator; iPhone = Satellite). Graduated to default-on 2026-05-18 — no flag required.
R2 — capability advertisement. Every device broadcasts its capability flags (audio start, BLE start, camera, archive) periodically. The popover above renders this cache.
R3 — operator-pinned finish-line iPhone. The Mac context menu on a connected iPhone lets the operator "pin" it as the finish camera; iPad filters detections to honor the assignment. Shipped, no walkthrough yet.
R4+ deferred: Mac SwiftData ModelContainer + Standby host replication; iPhone as Primary host with race clock; hot handoff between Primary devices; eventually TV-as-operator-surface.
This walkthrough is automated. The 5 screenshots above came from an XCUITest that drives the Window menu + Live Meet + chip + popover against a deterministic fixture. The menu screenshot hovers Live Meet before capture so the highlighted state is visible.

Cloud Sync chip (right of the role chip): shows whether the meet has a cloud-sync room joined, what the room code is, and how many other devices are subscribed. Tapping opens the Cloud Sync setup sheet. Walkthrough pending.

Meet menu (further right): edit meet, delete meet, switch active meet, export. The W1 awards-policy editor lives inside the Edit Meet sheet that this menu opens.

← All walkthroughs Home

Who's running the meet, at a glance.