Skip to content

Unify naming/ordering across providers for consistent UX #804

@coygeek

Description

@coygeek

Unify naming/ordering across providers for consistent UX

Description

Currently, each provider uses different terminology and ordering for their usage windows. For example:

  • sessionLabel varies: "Session", "5-hour", "Credits", "Claude", etc.
  • weeklyLabel varies: "Weekly", "Balance", "Usage", "Gemini Pro", etc.
  • opusLabel (tertiary) varies: "Sonnet", "Monthly", "Gemini Flash", or even nil
  • The internal keys are five_hour, seven_day, seven_day_sonnet/seven_day_opus

This creates an inconsistent experience when switching between providers or using multiple providers simultaneously.

Proposed Solution

Standardize on a unified naming and ordering scheme across all providers:

  1. Naming convention (three tiers):

    • Primary: session (5hr) — the short session window (five_hour)
    • Secondary: session (weekly) — weekly resets (seven_day)
    • Tertiary: session (monthly) — monthly resets (model-specific or credits-based)
  2. Ordering/layout:

    • Show session (5hr) as the primary progress bar (top/main position)
    • Show session (weekly) second (underneath the 5hr bar)
    • Show session (monthly) third (below weekly, or hidden if not applicable)
  3. When a tier is not applicable: Hide it gracefully (no empty/inactive bar)

Current Inconsistencies Examples

Provider Primary Secondary Tertiary
Claude "Session" "Weekly" "Opus" (model-specific)
Gemini "5-hour" "Weekly" "Monthly"
Amp "Amp Free" "Balance" nil
Kimi "Credits" "Usage" nil

Motivation

  • Consistency: Users know what to expect regardless of which provider they're viewing
  • Discoverability: Easier to compare usage across providers at a glance
  • UX coherence: The mental model is unified — "session" is the umbrella term, with duration modifiers

Alternatives Considered

  • Keep provider-specific names — rejected because it creates cognitive load when switching providers
  • Use icons only — rejected because accessibility and clarity suggest text labels are important

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:ui-uxUI polish, settings, layout, interaction behaviorenhancementNew feature or requestneeds-designValid request, but needs product or UX design decisionpriority:lowLow priority: minor bug, polish, or long-tail backlog

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions