4 ms·
I tried Spotify shortly after it was released. It was in a bad shape and missed essentials (e.g. basic filtering by name or in lists) to the point of being unus
by machomaster 3y ago
I tried Spotify shortly after it was released. It was in a bad shape and missed essentials (e.g. basic filtering by name or in lists) to the point of being unusable. I usually am an avid writer of feedback, but here it was clear to me (sic!) that devs simply lacked resources to implement all the essentials and they were coming in short time.
But imagine my surprise when I checked Spotify a couple of years later and the situation was still the same. Ok, I thought, they must have had different internal priorities, but once they get those, they will make UI at least semi-usable.
A few years passed, but the answer was still no. Once again I didn't write because clearly they must have had thousands of actual users writing and demanding the essentials and those things MUST be on their way, no way they weren't!
Several years later and the situation was still the same... This is when I stopped making excuses for the developers. They must be technically incompetent, be dim product-management wise (not understanding features, people, customers, lacking a vision, not to know how to collect, analyze and work on feedback) or stupid/unmotivated. But probably everything of the above.
I only criticize the technical aspects, not the business side. And I don't even criticize a much more challenging podcast/video side of things. I am merely talking about the lack of essentials in the basic music player. They couldn't even do that! I can bet money that the podcast implementation is on no better level. Other people's comments support that assumption. I am not surprised in the least.