[bertil]

The point is interesting, and follows the more general Lean approach. I can easily see how to decide not to implement a feature — what is less clear is how to address such requests: any public forum, related to features or not, will have tons of those, and they are usually the most voted comments (because they are positive, lead to discussion and refer to unmentioned aspect of the service).

Should the company be silent? Should they say that those are further down the pipe than other, non-visible aspects (better synchronisation, platform compatibility); should they say that those have been considered and will not be implemented in the foreseeable future?

[mkal_tsr]

The way I approach it with my users is there is a link on every page to report bugs and request features. Bugs get attention, features get considered. I also follow a [ feature ] -> [ tech-debt && bug fixing ] -> [ optimizations ] -> [ repeat ] and my users know that. Generally what I look for in the feature requests are trends and clusters of topics or pain-points and then I try to find the more common case that those multiple requests are all unified by. Once you find that, it's a lot easier to see if it fits into your overall roadmap / vision, and allows you to execute on it better.