"Like vs. replay" separation for music streaming libraries
Problem
Music streaming services conflate "liking" a song with "wanting to hear it again." One user reports hitting the dislike button on songs they love just to remove them from rotation, and YouTube Music makes it nearly impossible to bulk-edit a bloated Liked library full of duplicates. The distinction between taste archive and listening queue is not supported anywhere.
Opportunity
A third-party tool (or YouTube Music extension) that splits the library into a permanent "taste archive" and an editable "replay pool," with bulk duplicate cleanup, per-song expiry ("don't play this for 6 months"), and rotation controls the native apps lack.
Market analysis
A real and well-documented pain, but it lives entirely inside platforms whose data model actively works against it: likes and dislikes are the training signal for recommendation engines, so a taste/replay split is a feature YouTube Music is structurally unlikely to ship. Third-party tooling exists around YouTube Music (open-source clients, library managers), yet none implements the archive/replay separation, and all of it depends on unofficial APIs.
Market · Power listeners on YouTube Music and Spotify who curate large libraries; niche but vocal, evidenced by recurring Reddit threads asking for rotation and bulk-edit controls.
Pricing · Comparables are free or open-source (Music Assistant, InnerTune); realistic ceiling is donation-ware or a $2-5 one-time browser extension.
Pros
- + Pain is specific, articulable, and currently unaddressed by any verified tool.
- + An MVP can start as a bulk dedupe/cleanup utility, which is useful on its own.
- + Per-song expiry and rotation controls are features users repeatedly request.
Cons
- − Depends on unofficial YouTube Music APIs that can break or trigger ToS enforcement at any time.
- − The feature fights the platform's own recommendation data model, so it will never be absorbed, but also never stabilizes.
- − Tiny willingness to pay in an ecosystem where comparable tools are free.
Existing / similar tools
Source
r/SomebodyMakeThis (Reddit)
The subtle trap here is that “dislike a song you love” is not a UX bug, it is the platform’s business model: the button feeds the recommender, so splitting taste from rotation would degrade the very signal the service monetizes. That means a third-party tool is the only path, but also that the tool permanently lives on borrowed rails, since unofficial YouTube Music APIs have a history of breakage whenever Google tightens access. The strongest version of this idea is the boring half: bulk duplicate cleanup and a portable “replay pool” playlist the native apps can already consume. Do that as a one-shot web utility and you have a defensible beachhead; the six-month expiry and rotation logic can follow once users trust you with their library.