For a proper remote UI, we need at least the following functions in the integration of remood.js:

Basic player:

getPlayStatus - Returns the current status of the player ('playing' or 'paused')
setPlayStatus(status) - Sets the play status and returns the new state after completion. With that, we can visualise the delay until the music is really running.
playTrack(track_id) - plays one specific soundcloud item
nextTrack()
previousTrack()
getCurrentTrack() - getter for the currently playing item

Playlist:

playList(array of tracks) - plays a list of soundcloud items
playListItem(index)
addTrack(position, track)
removeTrack(position)

We might implement these two groups already into separate objects. I am sure that we will need more of these later on.

Currently we generated them on our machines and comitted them to the production branch

Sometimes I want to use a smartphone as the player and another one as the remote. Since it switches automatically at the moment, this is very user unfriendly.

We should display a pause button instead of an orange/active play button on the artwork when a sound is currently playing.

Just seen on mobile, didn't inspect further

Interface elements

Player

• Play
• Pause
• Volume

Searchlist

List of searchitems, grouped by item type with header (user, track, set, list...)

Searchitem

• artwork
• title
• specific styling for all types

List

• List of tracks

Playlist

• List of tracks

Currently the blade templates get compiled & rendered each time a request hits the server.

We should at least compile it to js functions in our build step, so we can just require them.
(Also the frontend will be able to use them in the future)

Remove bootstrap and replace it with a sane semantic layout structure based on flexbox.