Tape Music Suite

#project|
◇
#product
◼
#music
◆
#music business
◆
#user experience
◆
#frontend
◆
#react
◆
#react native
▽
#entrepreneurship

September 04, 2026

I have spent years accumulating music in my computers, then 7 years ago I started playing (djying) and after a few years I got to realise that the tech, and the experience of building your playlists, it was a deeply scattered world that did not premium to build something better cause the market was small enough to not premium innovation vs the amount of work that is needed to building something good enough. That changed in Jan 2026.

I started Tape Music Suite because I wanted to use the library on my desk computer on my phone, with ease. I wanted to browse the same albums, search the same folders, listen to the same tracks, and keep working on playlists while away from my desk. The open, and closed, source ecosystem for making this reliable, was a pain in the ass to setup, and a pain in the ass to maintain. Carrying the music on the phone is nonsense in the world we live in. After a few months of full research and product development, here we have it:

Tape Music Suite

Tape Music Suite running on desktop and phone

Tape Music Suite on desktop and phone.

The product

The first version of the product is deliberately close to the way I already work, but happens to be the needs of others as well:

  • I add the folders where I keep my music instead of uploading the collection;
  • Tape scans the library and builds a usable view over the files and their metadata;
  • I can browse albums, artists, tracks, history, and playlists from the desktop;
  • I can use the same library from the phone;
  • I can bring playlists and crates from the DJ tools I already use;
  • I can keep the local experience free from a remote subscription.

That list is not the project by itself. The interesting part is making these things feel like one piece of software rather than a pile of utilities.

I care about the small continuity details. A playlist should not become a dead export when a file moves. A missing track should be explainable. Artwork should not feel detached from the file that produced it. Search should work on the library I have, not only on the fields a streaming platform decided to expose.

These are not spectacular features. They are the parts that determine whether I trust a music tool with a collection I have spent years building.

Why

I began with my own frustration, but the pattern is not unique to me. DJs keep large local libraries because their work depends on files, versions, folders, playlists, and preparation. Collectors care about editions and metadata. Producers keep working files and references. Labels and radio people have archives that do not fit neatly into a consumer streaming account.

The common thread is not that everyone needs the same product. It is that the local library is already valuable before another service gets involved.

That is the audience I understand because I am part of it. I am not building a generic music app and then looking for a reason to use it. I am building around a library that already shapes my day.

Turning it into a public product

After a while and feeling it useful enough and start sharing it with friends, I decided to build it open and as a real product, the niche gap of this need is interesting enough and the tech effort is manageable now even with a small market.

Website: tapemusicsuite.com · Source: music-streaming-hub