Post by VS Admin on Apr 24, 2012 15:42:50 GMT -8
There have been a lot of great ideas posted recently on this forum. Unfortunately, we have also had to reject a lot of ideas for various reasons. We wanted to make a post explaining possible reasons that we may reject an idea.
Firstly, we want to make one thing clear: a rejection now does not mean that we will reject the idea down the line -- it just means it will not make the initial v5 release.
With over 15 million people using ProBoards monthly, we are working hard to accommodate all members in the best way possible -- by providing great functionality, while keeping things simple. While many ideas may be great ideas, sometimes we have to reject even these great ideas for various reasons.
Some of the things we have to consider are:
Speed
Each feature that we add impacts the loading speed of pages. We have to make considerations of what features are practical and which would add too much loading time to pages.
Usability and Usefulness
How complicated is the feature? How useful is the feature to the general population? Would adding this feature be too complicated in terms of management/administration?
Scope of Use -- Custom Codes / Template Engine
How many users would actually use the suggested feature? Would it have wide acceptance or be something that only a couple people would use? Due to how many people would use the feature, would this be better off as a custom add-on code? Many changes that have been requested can be done with very minor changes to the templates.
Server/Database Considerations
We have to pull a lot of data out in order to generate each page of the forum. Being able to get that data swiftly is extremely important. We want to keep our response times quick so that your page loads are instantaneous. Sometimes certain feature requests would require an excess amount of CPU or RAM on a server. We have to take in this important consideration.
Conclusion
Hopefully some of this helps explain a thing or too. By no means are we out to reject every idea that comes along. We do, however, have to make judgement calls based on this criteria.
Firstly, we want to make one thing clear: a rejection now does not mean that we will reject the idea down the line -- it just means it will not make the initial v5 release.
With over 15 million people using ProBoards monthly, we are working hard to accommodate all members in the best way possible -- by providing great functionality, while keeping things simple. While many ideas may be great ideas, sometimes we have to reject even these great ideas for various reasons.
Some of the things we have to consider are:
Speed
Each feature that we add impacts the loading speed of pages. We have to make considerations of what features are practical and which would add too much loading time to pages.
Usability and Usefulness
How complicated is the feature? How useful is the feature to the general population? Would adding this feature be too complicated in terms of management/administration?
Scope of Use -- Custom Codes / Template Engine
How many users would actually use the suggested feature? Would it have wide acceptance or be something that only a couple people would use? Due to how many people would use the feature, would this be better off as a custom add-on code? Many changes that have been requested can be done with very minor changes to the templates.
Server/Database Considerations
We have to pull a lot of data out in order to generate each page of the forum. Being able to get that data swiftly is extremely important. We want to keep our response times quick so that your page loads are instantaneous. Sometimes certain feature requests would require an excess amount of CPU or RAM on a server. We have to take in this important consideration.
Conclusion
Hopefully some of this helps explain a thing or too. By no means are we out to reject every idea that comes along. We do, however, have to make judgement calls based on this criteria.