Deep
Indie stores, labels, physical culture, and places where real discovery starts.
Product Case Study / Browser Extension Prototype
A working browser extension prototype that turns scattered digging into a lightweight system for capturing tracks, understanding tempo, saving context, and building crates.
Getting into DJing exposed a workflow problem: finding music is not the same thing as building a library. Tracks live across YouTube, Bandcamp, SoundCloud, DJ pools, streaming apps, radio shows, blogs, and long-form sets.
The more you dig, the easier it is to lose the context that made a track matter. Crate & Dig gives digging a memory.
Origin
I was learning the craft of DJing and needed a way to move faster without losing the human part of discovery. I did not want another heavy app. I wanted something that stayed out of the way until I needed it.
The best tools disappear into the workflow. Discovery should be fast, lightweight, and non-disruptive.
Crate & Dig detects music across supported sites, preserves listening history, shows tempo context, lets users save tracks into crates, adds tags, supports export, and opens source-aware ownership paths.
This is a simulated version of the extension flow. The actual product runs as a browser extension; this demo lets visitors feel the workflow without installing anything.
A lightweight export turns a digging session into something the user can review, share, or bring into another workflow.
title,artist,source,bpm,crate,tags
Add a short demo video here showing the real extension running across a music site, saving a track, showing BPM, and exporting a crate.
Crate & Dig was designed around the reality that discovery happens across stores, DJ pools, radio, blogs, sample tools, and streaming platforms.
Indie stores, labels, physical culture, and places where real discovery starts.
BPM was not just metadata. It helped build instinct around what different tempos feel like and where I naturally wanted to play.
The product problem was not only capturing metadata. It was making the tool useful without becoming another distraction.
Every platform exposes track information differently. The extension needed adapters, selector fallbacks, media-session metadata, and document-title parsing.
source -> media element -> track metadata selectors -> mediaSession -> meta tags -> title parsing
This public case study should include short, representative code snippets and architecture notes without publishing the full implementation. The goal is to prove technical judgment while protecting the product idea.
// Adapter idea source -> media element -> track metadata selectors -> mediaSession -> meta tags -> title parsing
// Storage idea content scripts stay lightweight service worker handles state, dedupe, crates, exports
Crate & Dig taught me that simple, well-built tools can have an outsized impact on a learning journey. The product did not need to replace DJ software. It needed to make the first mile of discovery less chaotic.
The right tool does not make the creative decision for you. It preserves the moment when the decision starts to form.
The larger vision is a full music-library workflow for discovery, organization, set-building, ownership, and creative memory. The case study starts where the pain was clearest: the browser.
Build better creative tools
I help teams turn niche creative behavior into lightweight, useful products people actually want to keep using.