Skip to content

Group member standings and social UI plan

Status: Implementation plan with the stats-sharing baseline completed on its recorded branch. Remaining UI work must be reconciled with the platform roadmap.

Audience: Product design, frontend engineers, accessibility reviewers, and QA.

This document records the next UI increment for Letter Golf Groups. It complements the Phase 5 section of the platform roadmap; where there is a conflict, the roadmap is authoritative.

Goal

When a player views a group and its currently selected activity, the standings show the status of every current member of that group. A member can be selected to see a deliberately limited, group-private summary. This is a competition context, not a public social graph.

Phase 5's only activity is the global Letter Golf Daily. The UI and component boundaries should be ready to represent a future Hole, Round, or Tournament without surfacing unfinished event navigation now.

Current data and immediate UI change

GroupResponse already provides the data needed for the first change:

  • members contains every group member.
  • todayStandings.entries contains only members with a materialized play state.

Construct standings rows from members, looking up an optional entry by userId. A member without an entry renders as Not played with no score. This makes the immediate change frontend-only.

Standings behavior

  • Show a compact summary above the list: 1 of 3 members finished.
  • For a player who has completed, show a small relative summary such as Your score: 3 · Tied for 1st.
  • Sort Completed members by final score ascending; tie ranking is shared.
  • Then show Playing members, then Not played members. Neither receives a numeric rank.
  • Each row has: rank or em dash, display name, (you) for the viewer, and the final score or text status.
  • Use the established vocabulary exactly: Completed, Playing, and Not played.
  • Not played is neutral, never a red, warning, or shame-oriented state.
  • Never reveal submitted words, partial scores, progress details, or solutions.

Suggested current rendering:

Global Daily · en-US
1 of 3 members finished       Your score: 3 · Tied for 1st

Standings
1   masojus (you)                                   3
—   Maya                                      Not played
—   Nico                                       · Playing

Group-scoped member detail

Make member names link to a group-scoped route:

/groups/[groupId]/members/[userId]

Do not create a public /users/[userId] route or a follower model. The route must verify that the viewer belongs to the group, then show only information appropriate to that shared context:

  • display name;
  • current selected-event state, including score only when completed;
  • group and event context, for example TestGroup2 · Global Daily.

On a phone this is a compact detail page with a back link to the group's standings. It should not be a dashboard.

Streaks and deeper stats

Current Daily streak visibility (implemented in private groups):

The group-shared stats projection now includes a player's current Daily streak for each group member, visible only within private groups. The streak is shown as a nullable field sharedStats.currentDailyStreakDays in the authorized group detail response. A streak is current (active) only if it was played today or yesterday on the Pacific Daily calendar; stale stored streak counters project as zero. A null streak value is reserved for a future visibility choice that hides the metric.

In the standings view, a positive current streak appears as subdued secondary-line text within the Player cell (e.g., 12-day streak beneath Maya), preserving one row/link per member and keeping Score and Time focused on today's event. The member detail page repeats the current streak and shows a neutral no-active-streak state for visible zero.

This initial increment applies only to Letter Golf and Reverse Cross Global Daily within private groups and uses a single bounded Cosmos read-many request (up to 50 group members) to avoid N+1 reads.

Private data boundaries:

Do not expose a member's full /me response, generic statistics dictionaries, submitted words, full history, or other non-allow-listed data. No public user profile was added; /users/[userId] does not exist. The dedicated member-scorecard endpoint now projects only the approved aggregate fields after group-membership authorization and server-side evaluation of the member's sharing settings. The complete design and implementation record is documented in stats-sharing-implementation-handoff.md.

Frontend direction for shared scorecards

The current frontend increment keeps game selection as a dropdown, not tabs, because Groups are expected to contain six or more games. Standings keep the flame treatment for positive current Daily streaks, and member names in both Today standings and the Members roster navigate to the same group-scoped member detail route while preserving the selected game query parameter.

The personal scorecards provide the canonical presentation shape for the shared detail pages:

  • Letter Golf highlights the Daily streak first, then all-time play, then score distribution. The longest-word metric presents the word itself with the length as supporting detail.
  • Reverse Cross uses the same Daily streak card first, then compact natural-height play and timing metrics, then board-size timing. The board-size table should comfortably support 5x5 through 9x9 rows and future timing additions.
  • Daily completion status on scorecards should be quiet supporting copy, not the green gameplay success banner.

Stats Sharing implementation record: Complete on feat/stats-sharing-2 at the handoff's 2026-09-12 snapshot; the handoff does not assert later merge or deployment state. Persistent per-game sharing defaults and per-group overrides are implemented on the backend with a complete authorized group member scorecard API and authenticated settings endpoints. The intended privacy boundary is group-private and user-controlled: no public profile route, follower model, submitted-word list, or individual play history. When Letter Golf details are shared, its longest-word highlight includes the word and length when known; there is no per-stat toggle in this version. Detailed game sharing is enabled by default with an opt-out; group-level modes are Share all scorecards and Current streak only. See the Stats sharing implementation handoff for the complete implementation summary, API contracts, and final acceptance checklist.

Future-friendly implementation boundary

Extract the display logic into a reusable standings component with generic selected-event inputs, rather than naming it DailyStandings. Phase 5 still passes Global Daily data and has only Today and Members navigation.

A future event may supply a heading such as:

  • Saturday Nine · Hole 4 of 9;
  • Summer Open · Round 2 of 4.

Do not add disabled Events, Rounds, Tournaments, Courses, or group-specific-puzzle UI in this increment. Phase 5 is Global Daily only.

Future nudge interaction

A later group-only nudge can help a member protect a Daily streak without becoming a messaging system:

  • Show Nudge Maya to play only for a member whose current event state is Not played.
  • Never offer it for Playing or Completed members.
  • Limit it to one sender, recipient, and event/day.
  • The notification is spoiler-free: no words, progress, score, or answer data.
  • The recipient must be able to opt out in Settings.

Do not ship an enabled UI that pretends to send a notification before the notification plumbing exists. A non-rendered or feature-flagged NudgeMemberButton component is acceptable, but it is not production functionality yet.

One possible later endpoint shape is:

POST /v1/groups/{groupId}/events/{eventKey}/members/{userId}/nudge

Its backend must verify shared group membership, enforce the rate limit, and respect the recipient's notification preference.

Guardrails and acceptance checks

  • A group with three members and one standings entry renders all three members.
  • Missing standings entries render as Not played.
  • Completed entries sort by score and receive correct shared ranks.
  • Playing and Not played entries have no rank.
  • The member-detail route is inaccessible to non-members.
  • Status never depends on color alone and member rows remain usable touch targets.
  • Existing group behavior stays spoiler-free.