Playbox
Treats Spotify as a provider rather than a platform: sets, tags and genres that belong to you, over a real library, with audio metadata pulled from open databases.
- Role
- Solo
- Period
- 2026
- Type
- Tooling
- Status
- building
Overview
Spotify is good at playing music and bad at letting you own how it is organised. Playbox sits on top of a real library and adds the structure a DJ actually needs — sets that are not playlists, tags that are not genres, and a sync model where pushing to Spotify is an explicit act rather than the source of truth.
Audio and metadata come from open databases — AcousticBrainz, MusicBrainz, Last.fm — so the organisation survives whatever Spotify decides to do next.
Modules
Library & sets
The domain distinction the whole product rests on: a set is a prepared thing, a playlist is a Spotify object.
Tags & genres
Your own taxonomy alongside the one the streaming service imposes, kept deliberately separate.
Integrations
Spotify for playback and library, AcousticBrainz and MusicBrainz for audio metadata, Last.fm for history.
Documentation discipline
Every doc opens with FACT or ASPIRATION. FACT files cite evidence and carry a last-verified date; only the vision and roadmap are allowed to speak in the conditional. Architecture decisions live as immutable ADRs, and a known-gaps register tracks dead code and open questions rather than pretending they do not exist.
Stack
- 01Next.js
- 02TypeScript
- 03Supabase
- 04Spotify API
- 05MusicBrainz