aesthetic.computer / core
Monorepo for Aesthetic.Computer aesthetic.computer
Star
Fork 0
Watch
core juke-wizard design source-browser-notes.md
2.5 kB
Markdown
at aesel-native-integration-plan

Menu Band Juke source browser #

Neo → Aesthetic → Spotify → Apple Music

  • Neo is the current computer name, shortened from Jeffrey’s MacBook Neo.
  • Aesthetic contains cloud releases. Publish and account actions live inside this tab.
  • Spotify and Apple Music each own their search, connection state, attribution, and errors.
  • Browsing another tab never changes the playing track. Only Play changes the persistent transport.
  • No global Cloud button and no mixed All tab.
  • DJ, waveform editing, notes, and local-file actions appear only where the source permits them.

FOSS case studies #

Project Source model Keep Avoid
Music Assistant Filesystem, SMB, Spotify, YouTube Music, and other services implement the same music-provider contract. One provider interface with explicit capabilities. Pretending every provider supports the same playback or mutation features.
OwnTone One browser and queue span local music, files, radio, podcasts, and Spotify. Persistent playback while browse context changes. Burying source identity after content enters the queue.
Moosync Local, Spotify, and YouTube share one desktop shell with source filters. Provider-scoped search and one visual grammar. Its repository is archived; use it as interaction precedent, not a dependency.
Strawberry Local collection and streaming services live in separate navigation branches. Clear source boundaries and service-specific setup. Making remote providers feel like secondary utilities in a dense sidebar.

Integration boundaries #

  • Apple Music is viable as a first-class macOS source through MusicKit for Swift: catalog search, library access, and playback are supported after user authorization. Menu Band needs the MusicKit App Service and NSAppleMusicUsageDescription before the tab ships.
  • Spotify stays a browse/playback source. Its developer policy prohibits mixing, remixing, overlapping, or integrating Spotify content with another service, so Menu Band must not expose Spotify tracks to DJ decks or effects.
  • Aesthetic and local files can keep the full Juke toolset because Menu Band controls those media paths.