[All Platforms] Changelog after each Update (In-App)

[liamwhear]

With each new update, no matter what gets added or taken away, there is a curious lack of accountability from the actual staff, and the (paying) userbase are left confused.

Why can we not drag from iTunes into our playlists anymore? Why can we not order our playlist columns as we see fit?

So a detailed, easily accessible, log after each update would sort this. In this log should be a list of all the changes made with each update, and with the reasons why the changes were made. This is most important.

We pay for this service. Why should we be left utterly confused with each update? We're left to scurry over to this forum, where your lackeys (who actually aren't on the development team) have no choice but to say 'I don't know' to each question, and with each request to implement back a feature in the Ideas section, the only response is 'This is not a priority'.

What's wrong with some honesty, eh?

[rlb89408]

Last thing posted in the news blog is on 2016/10/24 which was just updating terms and service. If it's just minor fixes tell us. We would like to know what changes with our application and this shouldn't be hidden behind a new blog.

[user-removed]

100% agree

[llysaur]

I'm on iOS, and I too get tired when I see new updates pushed **without any notice of what's been updated.**

What's the incentive for me to update? How do I know what I'm getting into?

I'm a busy person. I like to update mindfully. So I check the version notes. I don't always have time to go to the blog and search user forums, but I DO check the version notes in the App Store before downloading an update.

C'mon product team, product manager or dev manager, please update the changelog and version notes! I'd like to highlight that this administrative task is IMPORTANT to me as a user. I WANT TO KNOW WHAT HAS UPDATED AND CHANGED, AND IT MAKES SENSE THAT THIS INFO SHOULD BE IN THE VERSION NOTES.

[sindreg]

I **bleep**in love reading patch notes even when the software is working fine.

Have you guys seen https://labs.spotify.com/?

It gives the impression that the dev team at Spotify is only preoccupied with servers and infrastructure, but doesn't say the first thing about UX. The speed and uptime in Spotify is really impressive for sure, but that doesn't really make up for a stale interface and extreme lack of customer communication.

That news blog that Spotify recommends as an alternative to patch notes is ridiculous too - it's just a bunch of hip playlists and weird partnerships. There's no technical content and there's no indication that they're interested in pushing the envelope in UI or UX.

[gabrieltnetto]

I want my changelog!

[mannaux]

I am honestly shocked that anyone on the spotify dev team doesn't have time to send out a simple changelog for its users. Spotify, I will NOT update software that doesn't tell me what is being changed. Get your **bleep** together and put out a simple changelog for YOUR software.

[factorx]

I've asked for this before and I've finally concluded it is futile to insist. They are not gonna do it ever just because they do not want. It only takes 5 min to implement such a simple feature as a changelog but they do not like it.

After last year major bug I can only think one reason: Spotify has become a real blotch job and they do not want to publish a changelog because they are not interested in revealing their own wastes.

This total lack of transparency is really dissappointing.

[cuongnguyen]

Spotify used to have a descriptive log for every update, but now it has followed Facebook's footsteps. LAME!

[user-removed]

For my old student job, I developed a software tool---and even that tiny thing had a changelog for its little crowd of users! I cannot believe that a company such as Spotify is not able to implement that...

[ikd8ak3a3]

Yesterday I've posted:

https://community.spotify.com/t5/Closed-Ideas/iOS-Please-provide-actual-Change-Logs/idc-p/1651755#M4...

promptly I got a reply from a user pointing me here. The fact that it has been posted:

Submitted by liamwhear on ‎2016-06-02 10:46 PM  

And yet nothing has changed (over half a year later) goes to show that spotify does simply not care. It's not a new feature of technology that's being requested. It's simply meaningful changelog that could be simply put in place by executive order over the lazy dev that re-uses the same lame commit log every time. Look spotify all it really takes is to find the direct boss of that particular dev and tell him to take the finger out.

What a shame.