Skip to content

A Java/JavaScript-based fullscreen interface displaying your current music on Spotify in a beautiful little browser page

License

Notifications You must be signed in to change notification settings

Selbi182/SpotifyBigPicture

Repository files navigation

SpotifyBigPicture

A highly customizable interface that displays your current playback status on Spotify in a beautiful little browser page!

You might want to use this over Spotify's own (in my opinion, rather underwhelming) full-screen mode, or you can use it for your TV to give that outdated, low-resolution OSD a fresh paint job!

This interface is primarily read-only. Specifically, this means that you cannot actually control your music, beyond a few basic commands like play, pause, and skip (needs to be enabled in the settings first). This is both because of limitations to the Spotify API and because the idea is to set this app up once, and then it permanently runs as a pure information display.

An example where this is useful would be hosting a party where you want to let your guests see at any time which songs are up ahead, by putting a monitor near the dance floor that you connect to a Raspberry Pi.

Screenshots

These two examples only show examples of SpotifyBigPicture's default preset. For more screenshots, see the other presets!

Album View

Deafheaven - Dream House

Playlist View

Playlist View

Customization

Click the gear symbol in the top left of the interface to open the settings for Visual Preferences. Here you can customize the styling of the interface from a number of options with just a few clicks!

Your settings are automatically stored locally, so you won't need to worry about reconfiguring everything each time you reopen the website.

  • A full list of every preset can be found here: PRESETS.md
  • General information about the settings can be found here: SETTINGS.md

Installation

(If you prefer a video tutorial, click here)

Step 1: Create Spotify App

  1. Create an app on the Spotify Developers dashboard (you might need to create an account first)
  2. Copy the Client ID and Client Secret and save them for later
  3. Go to "Users and Access" and add your account there (name and email address)

From here on you can choose between one of two ways to continue with the installation.

Step 2 - Variant A: Manual Java installation

  1. After creating the Spotify app, click on "Edit Settings" and add the redirect URI for this app: http://localhost:8183/login-callback (make sure you click the little green "Add" button before saving!)
  2. Download the current release
  3. Paste the Client ID and Client Secret you've saved earlier into the respective fields in the spotifybot.properties file
  4. Open a terminal in the same folder as the JAR file (easily done by holding shift and right-clicking, then selecting "Open terminal here"). Then start the app with java -jar SpotifyBigPicture.jar

Step 2 - Variant B: Pull Docker Image

  1. After creating the Spotify app, click on "Edit Settings" and add the redirect URI for this app. Depending on where you plan to run the app, you must provide a URI that's reachable from the outside. For example http://ip-of-docker-machine:8183/login-callback. The login callback must end with /login-callback! Also make sure you click the little green "Add" button before saving
  2. Pull the Docker image: docker pull ghcr.io/selbi182/spotifybigpicture
  3. Run the Docker image. Insert the Client ID, Client Secret, and Redirect URI you have specified earlier into the respective fields, to pass them as environment variables: docker run --name spotifybigpicture -d -p 8183:8183 -e client_id=CLIENTID -e client_secret=CLIENTSECRET -e redirect_uri=REDIRECTURI ghcr.io/selbi182/spotifybigpicture
  4. Then run docker logs -f spotifybigpicture so you can see the URL required for the next step

Step 3: Login

  1. You will be prompted to log in. The app will attempt to open the browser by itself, but if it fails, take a look at the console output and copy-paste the displayed URL into your browser manually. It should like this: https://accounts.spotify.com:443/authorize?client_id=[...]&response_type=code&redirect_uri=[...]&scope=[...]
  2. If everything worked out, you're done! If you've chosen variant A, the app will be available under http://localhost:8183/ and if you chose variant B, it's going to be whatever server you've provided

Requirements

  • Java 11 or newer:
    • Download here (obviously only required if you're doing the manual java installation)
  • Monitor should have 16:9 aspect ratio:
  • A modern browser:
    • There are a lot of fancy bells and whistles attached to this app that simply won't work on older browsers. I primarily developed and optimized it for Mozilla Firefox, but it also works on Google Chrome. Not tested on any other browsers, so I won't guarantee full stability over there
  • Spotify Premium:
    • You can still use this app as a free user, but you won't get the full functionality. For example, getting your current queue is only available for Spotify premium users. For free users, only the current song can be displayed. For albums, more than a good guess of whichever song comes next is unfortunately not possible

Interface doesn't update?

The information is fetched from Spotify's API by polling it once a second. Unfortunately, there is no "proper" way of doing it, as webhooks for song changes (like Discord uses them, for example) are unavailable for the public API.

As a result, the connection might get stuck from time to time. The app will automatically try to reestablish connections when possible, which usually only takes a few seconds. To keep the interface appearance as smooth as possible though, the timer will simulate playback by keep counting up seconds on its own if a song is currently playing.

However, if the interface becomes completely unresponsive, try these approaches:

  1. Change the current playback context (e.g. changing from a playlist to an album)

  2. For whatever bizarre reason, simply clicking on the devices button in Spotify on your PC (not even selecting any different device, literally just opening the dropdown) sometimes forces the interface to catch up. This has been my go-to for fixing stuck screens, and it works surprisingly well:

dropdown

Support

If you got any problems, write an issue ticket on GitHub and I will gladly take a look at it :)

Alternatively, message me on Discord. My username is: selbi