

Now, this also means that when we are playing music through the Echo devices, we can also login to the Spotify web player account using Alexa’s own account credentials, and control the playback thanks to the Spotify Connect feature. I work away on business quite regularly and if anyone at home wants to use Spotify on the Echo, this saves them cutting off my account to play back with as an account can only play music to one location at a time multi-speaker set-ups aside of course. The Echo devices are almost always set to my Echo profile, but I chose not to link up my own Spotify account to it. We have several Amazon Echo devices around our home that we use for getting the news, weather, etc. I have an account for me, my wife has an account, my children each have accounts, and there’s a special someone who has an account who isn’t exactly human - Alexa. We’ll come back to that later.įirst, a little about my set-up.

But there was obviously something going on, and I’m not convinced that Safari can’t support Spotify as I’ve seen details of people using the developer tools to switch user agents. If it had included withdrawal of the native app, then I could have seen it being a market-play thing. I wish I knew why Spotify made their change. But this presented me with a bit of a challenge for a particular use case I have.

#SPOTIFY WEB PLAYER MAC PRO#
Now I used to be Chrome all the way on both Mac and PC, but since I got a new MacBook Pro last year which actually had what seems to be a reasonable battery life (compared to its nine-ten year old predecessor), I figured a switch to a power optimised native browser was worth considering. The native Mac app was still there, but if you wanted to web it up, you needed another web browser. They made some changes to stop it working in the Safari browser. Back in 2017, Spotify made a rather curious change to their web player app.
