9 comments

[ 3.0 ms ] story [ 28.8 ms ] thread
You should add a demo url so that we can see how it looks!
Since there is no demo and the repo looks super barebones (a loop which templates a list of mp3s in a directory?), do the upvotes mean that there is demand for an HTML based audio player?

What features would everybody want from such a player?

Also my question.

Maybe it’s because it focuses on semantic HTML?

i am currently using a very rudimentary player that is extremely lightweight, vanilla js, supports basic multi-room (multi-device, i.e. pick a track on your phone and listen to it from the tv) and defaults to repeat 1 mode. I want it to run without issues on old phones so i can just hook one up to the stereo. Considering adding drag and drop so i can listen to local tracks as well

(you clearly need some sort of server to do this, i am using mqtt because that's what i had laying around, but maybe this could be feasible with modern browser features skipping an external server?)

You could use websockets, but MQTT is a great and robust option
one of the first pages i ever put on the internet was a flash-based mp3 player with an iframe populated by a php script that scraped my local hard drive at home

loved showing off my music library on school computers, and a couple friends asked for the code to build/remix their own