decisiondecided

Keep two-click play without account

Context

  • A board game site’s drop-off rate depends heavily on whether a visitor can try something at the moment of curiosity
  • When sharing with others, requiring account creation severely reduces the reach of shared links
  • Parlourite’s value lies in engine generality, and “just try it once” is the entry point for communicating that value
  • At the same time, unrestricted anonymous access carries risks of abuse, resource exhaustion, and unmeasurable retention

Options

Baseline: standard mandatory sign-up model. Evaluation criteria:

  • C1: Low friction on first visit / C2: Shareability with others / C3: User privacy
  • C4: Abuse mitigation / C5: Retention measurement / C6: Implementation and operational cost
OptionC1C2C3C4C5C6Total
Mandatory sign-up (Baseline)0000000
Email registration with confirmation---++0-1
OAuth (Google etc.)00—++++1
Fully anonymous access++++++——0+2
Two-click immediate play + optional Passkey++++++-0-+4

Decision

Preserve an experience in which any game can be started within two clicks and without account creation.

  • From the top page, selecting a game and choosing an opponent (AI or seat) is enough to begin play
  • Account creation is optional, performed via Passkey only when the user chooses to
  • Guest-state match records and settings are retained in local storage and can be merged into an account at the time of creation

Rationale

  • Parlourite communicates its value through direct experience; a sign-up wall is fatal to that path
  • The ability to enter play directly from a shared link is the most powerful organic distribution channel for a project with no marketing budget
  • Connects naturally with the privacy policy (2026-10-18-privacy-by-default)
  • Abuse and misuse can be mitigated by Cloudflare Turnstile and rate limiting

Consequences

  • Positive: Lower first-visit drop-off, higher conversion from shared links, consistency with privacy design
  • Negative: Constraints on guest-data retention period and device dependency, ongoing tuning of abuse controls required
  • Follow-up: Automatic deletion policy for guest data is covered in Terms §5 and Privacy Policy §4; abuse control implementation to be recorded in a separate operational ADR