Skip to content

[UX][P1] One-click shared listening and wallet-later onboarding #90

Description

@knzeng-e

Goal

Make Dotify deliver social value before asking users to understand wallets, contracts, chains, or storage.

Product principle

A shared link should become sound and human presence before it becomes a Web3 lesson:

open link → choose/confirm a name → hear the room → react/connect → support or claim identity when useful

Scope

  • Simplify Home to three layers: Live now, Rooms, and Discover.
  • Choose one primary catalog representation; avoid rendering both a full Stage Rail and a full duplicate grid above the fold.
  • Open the player immediately on track intent, using aura/placeholder data before remote media is ready.
  • Replace silent spinners with semantic states: opening, checking access, loading first bars, joining, connecting audio, live.
  • Preserve guest room access without wallet friction.
  • Present blockchain actions in human terms: Support artist, Human pass, Transparent split, Publish release.
  • Show the real royalty split before payment and a calm confirmation after support.
  • Replace the single global transaction toast with an operation queue capable of concurrent upload, transaction, key, and room states.
  • Add accessibility, reduced-motion, keyboard, mobile thumb-zone, and dual Host/browser permission handling.
  • Add funnel analytics that respect privacy.

North-star metrics

  • Value-before-wallet rate.
  • Room-link open → first sound completion.
  • Time to first sound.
  • Shared listening minutes.
  • Repeat host and repeat listener rate.
  • Room → artist support conversion.
  • Unique artist-listener connections created.

Acceptance criteria

  • A guest can join and hear a public room without wallet or blockchain vocabulary.
  • The first useful action is visually dominant on mobile and desktop.
  • No loading state is silent or technically worded.
  • Wallet/signature prompts appear only when the user initiates an action that needs them.
  • The philosophy is embodied by the flow, not explained by several instructional panels.

Metadata

Metadata

Assignees

Labels

dotify-backlogTracked by docs/backlog/backlog.json and Project 5

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions