Files
AudioManagerClient/docs/mood-first-client.md
T

2.1 KiB
Raw Blame History

Mood-first redesign — client notes

The canonical design and decision log lives in the server repo:

Read that first. This file only records the client-side consequences.

What the client becomes

  • Moods are the only content model. No Library, no Longform, no mounted music.
  • All music is downloaded on the server from YouTube; the client searches and adds songs to a mood.
  • A mood has songs (collection) and recommendations (auto-downloaded, playable in radio, not permanent until added).
  • Playback mixes collection and ready recommendations using collectionPercent.
  • A mood needs at least one song to play.

Screens

Moods | MoodDetail | Search | Downloads | Settings

  • Moods: mood list, create, global search.
  • MoodDetail: songs, add music, recommendations (Add / Not interested / Retry), next batch, mood settings (query, genres, collectionPercent, recommendationCount 0–30, refreshHours).
  • Search: remote YouTube search, results over 10 minutes hidden, add to the current or a chosen mood, already-downloaded/in-mood badges, paste URL.
  • Downloads: device-side offline files, delete/clear, storage usage.
  • Settings: server/account/devices/logout (no scan UI).

Remove LibraryScreen and all longform UI.

State/API changes

  • Remove library, longform, longformResults, longformProgress, musicResults, local searchResults, playAll, playLongform*, resumeLongform, longform progress reporting.
  • Add remote search state (searchResults, searchTargetMoodId), add/remove song, recommendation add/reject/retry, mood song counts.
  • CachedState becomes version 2 with moods + mood details only; invalidate old caches.
  • SongDto gains videoId and thumbnail; loses folder/album-id/path/genres.
  • Cover art is song-keyed: coverUrl(songId).
  • Playback snapshot/history, desktop seek, Android media session, sleep timer and device downloads remain.
  • Offline mood playback uses device downloads and cached mood details.