Alrighty. I was just trying to get my questions answered about what testing you may have done to know for sure that it could be a simple firmware update, but you seem to be very upset by this, which isn’t my intent. I just wanted to know if my vote would actually be going toward the device I own or if we’re talking about a brand new machine entirely. Im just gonna move on. All the best!
I love the passion and care you have put into all of this @Cronos, I really do mean that. I’m curious to know what brought you to put so much time and energy into something that you don’t own?
I will say that Polyend have a pretty firm grasp on their Product Vision but are also very Agile in taking user feedback. They offer the options of Feature Requests here so people can request features and others can vote on it.
But a large scale proposition such as this from one persons vision, it’s like bypassing the Feature Request of the community and making more than a dozen feature requests in one shot. It is clear that this is not your intention and again I have so much respect for what you have done and the passion you put into it, but it’s your Product Vision. I think all of us Play Users have one, just not many that will take so much time and passion to bring theirs to the community as you have done.
I could see this kind of idea growing and/or focusing on a communities idea of a v2.0 as a collaborative effort with people on Backstage. Gather a crowd and get feedback!
In terms of gathering user feedback, Ableton has—in my opinion—a rather exemplary approach on their Discord server. Beyond simply sharing on a myriad of questions, there’s a wishlist that users can contribute to. Everyone can then vote on the suggestions. This obviously doesn’t commit Ableton in any way, as they prioritize the feasibility and consistency of their approach. But it provides a (relative) transparency that’s useful to everyone. It’s not a model to be followed, but it’s a great source of inspiration.
This is pretty much the exact same system we have here on Backstage ![]()
I hadn’t noticed that. I was going straight to the play+ tag
. I’m sorry.
Thank you for the information.
I’m saddened to see people interested this device and they are spending time proposing improvements that seem to fall into a void. At the time that development seems to have stalled, while new products keep coming out.
I cannot help but feel that many of us have effectively acted as beta testers for features that never fully matured.
So instead of asking for more official updates, I’m asking for something simpler:
Please give us a way to load our own firmware, even with a clear “void warranty / use at your own risk” warning.
That alone would allow the community to continue development without any cost or responsibility on your side.
Right now the device is locked in a state that likely won’t evolve further. Opening just this one door would extend its life significantly.
Please polyend, do this!