Improve Algoriddim Communication About Most Requested Features

[Davidv100]

Hello,
We are fortunate to have a highly engaged community brilliantly animated by our beloved @Slak_Jaw . We have this Suggestion category, with a nice voting feature.

However, I guess it is also fair to say that we do not receive much feed-back from Algoriddim about most voted requests. The top three has gathered more than 100 votes each, and are open since 2020 or 2021, but we know close to nothing about their status.

To keep the Community as engaged as it is, and to confirm this voting feature has a real purpose, it would be nice to have a regularly updated feed-back from Algoriddim. At least confirming whether these are really being approved, considered, or rejected.

This kind of table would be helpful (real data).
Note that two out of the top three have been initiatiated by our animator @Slak_Jaw himself.

To be concrete, can we please have an update on the top three.
At least about number #2 and #3, as I think there is more communication ongoing about #1, if I am not mistaken.

Honestly, I think it is not much to ask, and actually long overdue, taking into account the votes amount, and the opening dates (these are now five or six years old).

Thank you.

[Slak_Jaw]

Thanks for sharing @Davidv100. I’ve already been discussing this with our development and engineering teams. I’ll see if they can provide some more details on these 3 topics in particular.

As for our voting system, please refer to the linked topic below for more general information on how this currently works:

Update to Our Voting System Guidelines [Suggestions]

As a user, it’s essential to grasp the significance of your vote and how it influences our development roadmap. When you vote for a specific feature request or general suggestion: Your vote signals your interest and support for the proposed feature/suggestion. We consider the cumulative votes alongside other factors such as feasibility, resource availability, and alignment with our product vision. While high-voted features are more likely to be prioritized, they are not automatically im…

[Davidv100]

Thank you, @Slak_Jaw , as always.

Obviously not all requests will lead to concrete developments.
High costs developments, even with high voting scores, but for which Algoriddim doesn’t see a global interest for the company will not happen.

I think topic #2 and #3 are relatively low cost.
Of course, this intuition, as well as interest for Algoriddim has to be taken into account, we all understand this.
It is also the reason why we would expect Algoriddim to say : “Look, this one has been rejected, we don’t like it, or it cannot be done”, or whatever. But at least say it.

You can definitely count me in as a realistic client, understanding all this, but still demanding, as I think it is good to be demanding for the software and the company to have demanding clients (look at Apple).

To be totally honest, topic #3 (performance pads display) seems such an obvious think to do, that I sometimes suspect the reason for not doing it is not technical, but something else. Like, is not doing it part is part of the collaboration with Reloop for the Reloop Buddy (as it is the only hardware on the planet fully supported).

Even this would be something we would understand.
But 6 years of silence, no. Same for #2, Soundwitch.

[Slak_Jaw]

You’re welcome @Davidv100. Thanks for the additional explanation and information. I appreciate it and will ensure this is communicated to the rest of our team. Thanks!

[damofinn]

Hey, I originally wrote a version of the post below in reply to a thread about a roadmap, but it’s been sitting in my drafts for a few months now. But I figure it’s worth adding my thoughts here, given its close relevance. Of course, this is just my opinion based upon my own experience.

---

As somebody that has worked in the software industry (game dev) for many years, I can appreciate both sides of the situation here. Developers need to strike a balance between communication to their end users, yet need to consider the commercial aspects of publicly committing to future development, which could potentially jeopardise their return of investment.

Having said that, purely from a user POV, having come back to Djay from Rekordbox over the past few couple of years, I am disappointed in the lack of visibility into the progress of user requested features. Taking a quick browse through this forum I’m seeing the development of a number industry standard (i.e been availble on other platforms) features and basic functionality that has been stagnant, in a number of cases, for many years. As a user, not knowing whether a feature is being worked on, where it sits on the priority list and whether or not its ever likely to see the light of day, is very frustrating.

As others have pointed out on this (excellent) forum, the competition do release dev roadmaps, so it’s not unusual.

The best loved software companies tend to be open with their users, bringing them along on the journey, with the confidence that they are great at what they do and no matter what the competition does or knows about their development, they truly believe in their product.

Please don’t take this as a criticism of Algoriddim, the work that you are doing or how you interact with your users. I highly rate Djay as a usable, reliable and open product, which is why I came back to it when I started up DJing again.

Communicating that you understand your users priorities and your short/mid/long term intentions to action against them can make all the difference in retaining and growing your current user base.

Kind Regards,

Damian

[Slak_Jaw]

Thanks for sharing this detailed feedback @damofinn. I appreciate it and will include this in my discussions with our dev team. Thanks!