As the new "nice" latest well talked version of SPotify became a rather hot topic, as past updates I've been thinking similar thoughts as some of my peers: "Why did they changed this or that?"
A solution to many of this problems, or sort of is the option of options.
Atm there aint A proper option other than uninstalling current version and downloading a previous version in which the user were satisfied with.
Meanwhile alot of users asking/demanind X service/option to be back or turned off. Why just simply not put that option instead of "cleaning" it out?
Alot of other applications often offers beta-versions or development option to be clicked where either A)new features can be seen or tested, or B)Old features can be seen, to be compared with a new/sharper version of the app/product.
Alternativly, as I pointed out in some other comment, is to put these changes/options as an in-app, as perhaps a program layer, where the user can modify the program as it fits the user. (And as sadly as it may sounds, to release some of the responsibility and load off the devs shoulder, to add some disclaimer sayin "use this on your own risk" or saying its experimental)
However, as a somewhat dev myself, it is alot more to code an add-in than simply just freakin add optional tools directly on the settings of the program.
I admit I felt rather disappointed to see that a program, as I understand, in the start to be a music program to have sold their soul almost entirely to social media, to the degree where in the settings have more options to socialmedia than the program itself.
So to sum it all up, my suggestion is:
-Offer more application options in the settings as for examples: User can choose behaviour of close buttons (to close app or put in system tray), where volume button to be (left or right side), search alternatives (as in search levels or search on/off)
-Offer a directly in the app feedback button, simliar done to mobile products, where the feedback is on release (for documentation reasons and offload, limit it to simple numeric values and refer to forum for further comments)
-If neither of the above, offer a kind of development version or option where ALL features old as new are listed, where users can on own risk( of program misbehaviours and crashes. This option not offering any particular support) choose the settings they want
-Lastly and alternativly, ALWAYS, if it falls within the category of user security, the possibility of revert to a certain release of the program, preferely within the program (if necessery, with disclaimer of that a previous version doesnt include in end-user support)