Skip to content

Latest commit

 

History

History
22 lines (17 loc) · 1.86 KB

File metadata and controls

22 lines (17 loc) · 1.86 KB

Design Context

Users

Rhythm game players (maimai DX / CHUNITHM) who want to track their daily play habits and rating progression. They're data-literate gamers who understand concepts like DX rating, chart constants, and score thresholds. Context: checking the dashboard after an arcade session or before one to decide what to play.

Brand Personality

Clean, utilitarian, data-forward. The dashboard is a tool, not an experience. Three words: precise, quiet, functional.

Emotional goal: confidence through clarity. The player sees their data, understands their trajectory, makes decisions. No hype, no gamification of the gamification.

Aesthetic Direction

  • Tone: GitHub Insights / Wakatime — the data speaks, the UI stays out of the way
  • Theme: Dark, but not the GitHub-dark clone currently in use. Open to the brand's own palette: purple (#863bff) from the favicon, game-specific pinks (maimai) and blues (chunithm)
  • Reference: GitHub contribution graph — clean grids, threshold-based color scales, information density without clutter
  • Anti-reference: Arcade-neon aesthetics, over-styled game portals, corporate dashboards with excessive chrome

Design Principles

  1. Data first — Every pixel should serve the data or help the user act on it. Decorative elements must justify their existence.
  2. Game identity through color, not ornament — maimai = pink spectrum, chunithm = blue spectrum. That's enough to signal which game you're looking at.
  3. Quiet confidence — Restrained palette, clear typography, generous whitespace. Let the heatmap and charts be the visual centerpiece.
  4. Functional density — Show meaningful information without scrolling. Prefer compact, information-rich layouts over spacious hero sections.
  5. Progressive disclosure — Summary at a glance, details on interaction. Don't overwhelm on first load.