Another thing is that this feature request thing has been going on for months and not even 200 post but they can't even keep up with that?
Imagine if Facebook did the same, they'd have 100s of 1000s of messages. You have 0 excuse pandora.
In the Pandora Community we know the value that our users bring because we talk to them every day. Our listeners are often the first alert for issues with our service, and we've always done our best to circulate your feedback on bugs and feature requests internally. Part of the reason we built this Community was to create a more accessible and visible environment in which to share the thoughtful feedback we get from our listeners constantly.
As far as developing these ideas, we take it seriously. We know we have to be very thoughtful when making changes to our product; what may be one user’s biggest concern could degrade the experience for someone else. We’re doing our best to bring benefits to all of our users.
Take for example our recently-introduced Pandora Modes feature. We took your feedback that certain Pandora stations were too repetitive, or that others didn’t feature the seeded artist enough, and we turned it into something new: we created modes that allow you to fine-tune your listening experience. With modes like Artist Only (for times when you just want your seed artist), or Discovery (when you need something fresh), we’ve answered both requests. It took us awhile to develop, but we’re really proud of the result.
So, you’re right: we can be slow to bring to life the great ideas we see from you every day. But we’re always listening, and talking internally, and figuring out what high-quality solutions we can bring you. For now, we hope you’ll keep posting your requests and up-voting the ones you agree with. The more up-votes a request gets, the better we can advocate for its development.
I've been a software developer for 25 years.
The time it takes to look at a request, determine its importance vs other issues that may be pending, put it on a business plan for the quarter, assign someone to the task, figure out how to make that work with the existing code base, test it, make sure it actually works and schedue it for some kind of release is not instant.
You can rest assured that any company that works at all on Internet time is worried first and foremost about the stability of the product, getting features rolled out that were planned in advnace, and then looking at enhancements.
Nobody is ignoring you. (I don't work for Pandora at all, disclaimer here) But I'm sure that they, like every other software company on the planet, has a six to twelve month backlog of feature requests to consider even before others throw them on.
Sometimes something can be done really quickly - like for example if there was text that was red and green to determine stop/start and that was not working for colorblind folks, switching to an icon is relatively simple. But messing with algorithms, making changes to workflows, and so forth - you can't just throw code changes into the mix and move on, unless you want the next complaint to be "why did this stop working? When is my radio coming back on?"
Even the best companies have this happen- anyone remember when Amazon went down for like, a really long time back in the day? That cost them millions. Nobody wants that to happen to their company, so these things can take time.
Also consider the workload developers face - there's never enough of them because to be honest there's always shortages.
Hang in there.