Shared hubs and shared collections
Make shared links and shared hubs mature into a cleaner way to follow music from other people without collapsing it into your main library.
Music Hub is personal software: a desktop-first phone companion for people who collect music seriously, prepare sets, and care about the archive they have built over years.
I am an indie developer, product designer, DJ, and music obsessive. I started building this because I had wanted it for years for my own collection. Now I finally have the output power to finish it the way I would love to use it, and while testing it I had the obvious moment: this has to be a product.
I understand the workflow from both sides: the technology side of building software and the music side of digging, sorting, preparing, listening, and eventually taking tracks back into the tools used to play.
The direction is practical and long-term: keep the archive on your computer, make it useful from the phone, and keep improving the way serious collectors and DJs move music from discovery into a real library.
These are the bigger product directions after the launch version: better library work, better DJ handoff, and broader platform support.
Make shared links and shared hubs mature into a cleaner way to follow music from other people without collapsing it into your main library.
Build the peer discovery network so Music Hub instances can find each other, route shared links, and connect paired devices without manual DNS, VPN, or domain setup.
Make away-from-home listening smoother with clearer setup states, better diagnostics, and less manual configuration.
Smarter ways to understand, rediscover, and work through your own collection, powered by local hub tools under the hood.
Explore local music embeddings and safe shared metadata so discovery can become more personal without turning your private library into a public catalog.
Persistent analysis plus review flows for duplicates, preferred copies, and library cleanup without blindly rewriting your archive.
Import and preserve more DJ-specific fields such as key, BPM, grid and cue information, with local analysis when metadata is missing.
Harden the internal extension points so future sources, add-ons, and experiments can plug into the product without ad hoc wiring.
Research and build a direct app-to-app remote mode so a paired phone can find the desktop hub without Cloudflare, Tailscale, or manual domain setup.
Continue maturing the desktop hub and companion experience across macOS, Windows, and Linux.
Join the launch community, send feedback, or tell me how your real music workflow works. This product should be shaped by people who actually live inside large personal libraries.