Contact person: Advanced Court Scoreboard Pairing System

Phone:Show

Email:Show

Location: Doha, Qatar

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"1) Purpose
Allow any watch/phone to quickly pair with the court screen using a short PIN code or QR code, without needing AirPlay/Chromecast.
Provide a Mirror Mode option to show the scorer’s watch/phone interface on the screen (for training/demo purposes).
2) Roles
Host / Court Screen: The TV/app that creates the session and shows a PIN.
Controller / Scorer: A watch or phone that inputs the score.
Spectator: A device that joins in read-only mode (view score only).
Admin: Approves/blocks controllers, manages sessions.
3) User Flow
A) Session Creation (Court Screen)
Reception/admin opens the scoreboard app for Court 4 → it shows a 6-digit PIN + QR code (rotates every 60–120s).
Screen message:
Join via: [login to view URL]
Enter PIN: 834 119
Or scan QR.
B) Joining (Scorer: Watch/Phone)
Phone: Open app → “Join a Screen” → enter PIN or scan QR → request appears on the TV: “Khalid requests control.”
Apple Watch / Wear OS:
App → “Join via PIN” (6 digits), or inherit session from paired phone.
Once approved, main buttons: +1 Team A, +1 Team B, Undo, Swap Server.
Approval: Default setting requires Admin/Host approval for the first controller (can be disabled for casual matches).
C) Joining (Spectator)
Enter the same PIN or scan QR → opens a read-only live scoreboard.
Screen may show “Connected viewers: 12” (optional).
D) Mirror Mode (Optional)
When enabled, the scorer’s watch/phone interface is displayed in a corner/side panel on the TV.
Use cases: demos, training sessions, exhibitions.
Best practice: disable during official matches.
4) Security & Control
Ephemeral PIN (TTL 60–120s) + signed QR code.
Role-based tokens: Display / Controller / Spectator.
Controls:
Max 2 controllers per court (configurable).
Admin can view connected devices, approve, reject, kick, or lock to read-only.
Anti-abuse:
Rate limiting (cool-down between point inputs).
Reject conflicting inputs.
Privacy: Mirror Mode masks any personal data.
5) Offline / LAN Mode
Screen generates PIN locally (e.g., C4-825311) when offline.
Pairing/auth happens over local Wi-Fi via WebSocket/MQTT.
When WAN is back, syncs to the cloud with event log reconciliation.
6) Performance Requirements
Session creation and PIN display ≤ 300ms.
Joining + approval from watch/phone ≤ 2s.
Support up to 100 spectators without slowing updates.
Score change → reflected on screen ≤ 300ms on LAN.
7) Conflict Handling
Event-sourced log with timestamps and sequence IDs.
If two controllers send the same point within 150ms → count once.
Undo reserved for highest-priority controller (latest approved, or Admin).
Game/Set/Match point requires confirm (haptic vibration or double-tap).
8) Screen UI (when idle)
Club logo + join instructions:
“Join at [login to view URL]”
“PIN: 123 456”
“Scan QR to control or view”
Countdown timer for PIN expiration + “Refresh PIN” button.
9) Admin Panel UI
Live Pairing tab: lists connected devices (type, name, role).
Buttons: Approve / Reject / Kick / Promote.
Toggles: Mirror Mode ON/OFF, Lock Court.
10) APIs (example)
POST /api/sessions → {courtId} -> {sessionId, pin, qrUrl, expiresAt}
POST /api/sessions/{id}/join → {deviceId, role=requestedRole, pin}
POST /api/sessions/{id}/approve → {deviceId, role=Controller}
WebSocket: wss://.../sessions/{id}
Events: POINT, UNDO, GAME_WIN, SET_WIN, LOCK, KICK, MIRROR_TOGGLE, STATE_SNAPSHOT.
11) Acceptance Criteria
PIN appears on screen in ≤ 300ms.
Watch joins and becomes controller within ≤ 2s.
1 screen + 50 spectators update with no visible lag.
Works fully offline on LAN; syncs when internet returns.
Mirror Mode shows scorer UI, hides personal info, and disables instantly when toggled off.
12) Watch UX Notes
Apple Watch: 6-digit PIN input via Digital Crown/number pad; fallback via paired iPhone.
Wear OS: simple PIN entry screen + haptic confirms.
Scoring UI: Two large buttons (+1 Team A / +1 Team B), Undo button, server swap.
Optional swipe gesture for Undo.
13) Example Copy (on screen)
“Join at [login to view URL] — PIN: 834 119 — or Scan QR”
“New control request from Khalid — [Approve] [Reject]”
“Mirror Mode active — for demo use only”
14) Roadmap
Sprint 1: Sessions + PIN/QR generation + spectator join.
Sprint 2: Controllers join via watch/phone + approval flow + device list.
Sprint 3: Mirror Mode + offline LAN pairing + stress tests." (client-provided description)