I am sure someone may have requested this before, but please consider setting up a token system for feature requests.
A token system would allow you to allot a certain number of tokens per cycle to registered Cubase owners that they can use to vote on feature requests that they really want. Users could use one or all of their tokens for features that you have marked as under consideration for development.
All forum users could still enter feature requests as often as they like but the tokens would be used for those requests that you have deemed worthy of your development time.
I think there are a few major advantages to this:
We as users would be aware of the features that you are actually considering.
We as users would be more aware of which features are truly gaining the most traction with other users. The post counts in a thread are
sometimes misleading due to posts that are conversation related and not necessarily a +1 or vote for the request. Requests could be ranked by
those with the most tokens making them always default to the top of the list.
You as a developer can easily track which feature requests are the most wanted and needed by your existing / paying customers. Currently, we
users can +1 100 different requests leaving you to have to sort through and guess about our true priorities. Users would have to carefully consider
the requests that they vote for which would help you to focus in on the features that are most important to us. The surveys are nice, but I see this
another tool that you could leverage.
Any non-implemented requests that have over a certain number of tokens could be carried over to the next cycle so that the users don’t have to keep re-entering the same requests over and over. Any tokens used for feature requests that are not implemented could revert back to the user to be used on the same request or a different request in the next cycle. That way if their request didn’t make the final cut, they would feel that they had a better chance to get a feature they wanted added in the next cycle by virtue of their token count would be higher than someone that did get a feature added in the previous cycle.
You could offer a certain number of additional tokens to customers when they upgrade to the newest version as an incentive to stay on the most current release.
I realize that you have to continue to develop to attract new customers as well, but this would allow a fairly low maintenance way to keep your finger on the pulse of your existing customer base. I think the users would appreciate this as well because it would make us feel like we are a bigger part of the development process.
Does anyone else have any comments on this idea?