It's mostly that I want my own list management, key combinations, navigation, etc. Once the entire UI is my oyster, I realized I don't have to settle for how someone else decided to lay out the menus, etc. 25 years ago I would just learn all the key combos and be set, but 12 major iterations later, few to zero of those UI skills and muscle memory state has survived. So now, I can do my own and no one can take it away from me :)

▲

hedora 3 hours ago | parent [-]

I strongly recommend going this route (speaking from experience).

It is shockingly easy to build an opinionated UI for these things in a web browser. You need to implement m3u generation (or use a js web player), and some sort of hierarchical hyperlink based nav that matches your muscle memory. You should be able to use an existing service to grab cover art and metadata for newly ripped disks (unless those services disappeared over the years).

If you want to use a native GUI/TUI toolkit, I’d be shocked if an LLM had any trouble laying it out after a few rounds of refinement. (It definitely will not have any trouble doing this for web stuff.)

	▲	titzer 2 hours ago \| parent [-]
		I've been vibe coding some music tools and after some researching let Claude get going with imgui (https://github.com/ocornut/imgui) to build a tool I use for local authoring. It's pretty pixel-dense and looks alright to me. It runs on MacOS and Linux, which is enough for my needs now. Claude has been pretty decent at getting audio stuff going on MacOS and can even tap into various accelerators in MacOS libraries. It's had no problems loading and playing mp3s and m4as, which is the majority of my collection. I'll probably prototype an music manager off of that. It'd be great if it works out for Android as well.