Actually I believe one of the worst things a tech company can do is have a public roadmap. There aren't many good reasons to have it, but there are plenty to not have one. Having one just puts pressure on developers, because the next question will be "when will it be available? Then they have to come up with a deadline. Then they are forced to get everything done in time, which is generally bad for creative work and quality. If the deadline isn't reached, that makes it even worse. Now the same people that asked for the road map and deadline will be the biggest complainers.
Another problem is that you basically show your competition what your future plans are, now, if they have more capital and people working for them, they can copy your ideas and release their version even before you did. And finally, it's a bad marketing strategy. Keeping future features and products secret creates rumor, which creates attention and anticipation. As an example you can look at Apple, who have practiced this principle to perfection.
So, public roadmaps... IMHO generally a bad idea in this business. The simple fact is that developers are probably working hard, people just have to have patience, post their suggestions and ideas, and regularly check the HYS sub-forum.
Another problem is that you basically show your competition what your future plans are, now, if they have more capital and people working for them, they can copy your ideas and release their version even before you did. And finally, it's a bad marketing strategy. Keeping future features and products secret creates rumor, which creates attention and anticipation. As an example you can look at Apple, who have practiced this principle to perfection.
So, public roadmaps... IMHO generally a bad idea in this business. The simple fact is that developers are probably working hard, people just have to have patience, post their suggestions and ideas, and regularly check the HYS sub-forum.