shared-jukebox's Introduction

shared-jukebox

A collaborative jukebox system being used in our office environment. It allows a group of people to connect to a central, known service to control music playback.

The system consists of 3 components:

A centralised ExpressJS + socket.io server which fields all requests and serves the web client, found in /server.
A web client that is used by end users to see the current playlist and request new songs, found in/web-client.
A music client that is run on a system with mopidy installed that can connect to the server to fetch the playlist and play music.

The server and music client may be on the same machine.

shared-jukebox's People

Contributors

Stargazers

Watchers

shared-jukebox's Issues

Add unit tests

Web client has some unit test coverage but the rest is very poorly covered.

Track the number of times “Let It Go” is requested

Detect song by the song ID.

You can have a scoreboard for the number of times it’s played and not skipped in a single session.

Start playback if track list is empty and a song is added

Based on user research:

The user will add tracks to the list
Music does not play
The user closes the application as it is “not working”

It would make sense to start playing a track as soon as it is added to an empty list to alleviate this and keep it in line with other music player behaviour. The pause button is available from all screens anyway, if required.

Recommend Projects