Fine with me. I still resent Spotify for buying up podcasts and locking them behind their app.
I hear you, but that style actually catches a lot of flack for the platform developer (Apple, in this case.)I don't agree. Let Spotify manage their own app, like any other developer and/or company. I'd rather Apple, and any company really, focus their attention on getting their things done.
That's what i did literally because of this bug, but can't listen Spotify exclusive podcasts which is a big con.Or, you could update to watchOS 9 and switch to Apple Music for a best-in-class listening experience.
You actually believe Apple has the resources to test 1.8 million apps for compatibility with new oses?How does Apple with all of it’s resources & beta testers not catch this before the final public release?
Thank you, this is the point the other poster seems to be missing. It's a CYA/PR move for Apple to do this.I hear you, but that style actually catches a lot of flack for the platform developer (Apple, in this case.)
Reframing the situation slightly, something used to work on an old system but doesn’t work on a new system. We in these forums will nit pick it apart but to an end user it looks like this
1) Spotify working great!
2) Do update from Apple.
3) Spotify stops working as it should.
From their perspective the Apple update broke what was working and their reaction is “$@&% Apple.” Most users don’t know or care that betas exist let alone could blame the app dev for not testing on them.
Truly, this situation looks bad for everybody. So while Apple shouldn’t have to test Spotify it behooves them to do so to prevent upset users.
I realize nothing is free, but ad supported Spotify is a horrible listening experience.
So much that I'm trying Apple Music again.
And even with bluetooth quality audio, the difference is noticeably better on Apple Music.
I'm not missing the point; I just don't agree with it.Thank you, this is the point the other poster seems to be missing. It's a CYA/PR move for Apple to do this.
It’s a tricky situation as a platform dev (which apple is in this case). From an end user perspective Apple is at fault. On watchOS 8 everything worked. After the update, Spotify broke. It looks like Apple broke it at first glance. From a PR perspective it is bad for apple (and also Spotify).Not that it matters, but I don't agree with that approach. It's why we still have legacy code lying around and XP lasted so long. Let the developers own the code they develop.
That's fine, but you can't expect consumers to think past the surface level of "iOS update broke Spotify". These are the same people that think that when the newest iPhone drops Apple pushes out some tinfoil hat conspiracy update to kill their old devices. We're talking about the general public here, not tech forum dwellers.I'm not missing the point; I just don't agree with it.![]()
Sure, I expect that. The user has the ability to contact the developer for support within the App Store. Based on app reviews, where users mention that updates break things, it appears they understand how this works.That's fine, but you can't expect consumers to think past the surface level of "iOS update broke Spotify". These are the same people that think that when the newest iPhone drops Apple pushes out some tinfoil hat conspiracy update to kill their old devices. We're talking about the general public here, not tech forum dwellers.
Good advice. Spotify is a great service but they were incredibly late to the Apple Watch apps to begin with and then when implemented it has never really worked that well. It always takes fiddling with but this is ridiculous that Spotify can’t own that their developers are horrible. I’m super frustrated.This is bs. I just got my last month of spotify premium duo refunded over this and encourage others to as well. It was easy - just started a support chat and they took care of it in a few minutes.