To control playback, you need to do two things

With this setup, spotify-tui can control all your Spotify devices. You can think of spotify-tui as more of a 'controller' or 'frontend' to Spotify. This app uses the Web API from Spotify, meaning that spotify-tui doesn't handle streaming itself. LimitationsĪs I've noted in the README, there are some limitations. Whereas spotify-tui runs in the 2-4MB range! I've observed the official client using 200-400MB. But so far the speed of the app has been excellent! LightweightĬompared to the official client app from Spotify, spotify-tui runs with low memory usage. And I've probably implemented things in an inefficient manor. Then of course, because I'm using Rust, there is the speed that you get out of the box.Īs of writing, I've made no optimisations to speak of. When I then had the opportunity to go online, everything 'Just Worked'.Ĭoming from a Javascript background, this developer experience is the dream. I was guided by the strong types and compiler checks. I built a large part of this app whilst offline during the evenings of a recent holiday. I've had tremendous amounts of fun working on this project.

As well as get more experience building advanced terminal applications. But I took this as an opportunity to get better with the Rust programming language. Some projects building a tui for Spotify already exist. I'm also a user of Spotify, so it's natural to me that Spotify is controllable from within the terminal. At this point, it's almost painful that I need take my hands off of the keyboard and use the mouse. Over the past couple of months I've been working on spotify-tui - a Spotify terminal user interface.Īs an avid terminal/tmux/vim user, I get frustrated when I need to leave the terminal to use certain applications.

What is spotify written in