I do read and think about all the feedback I get - and am extremely thankful for it. Remote Buddy today wouldn't be what it is without it.

What I can't do any longer, however - and I regret this myself - is to give direct feedback in the form of "that's already in the making" or "I'll add this to a future version and put it on the todo list for now". In the past I've never done so if it wasn't actually the fact or - respectively - it was my honest intention at the time to implement that feature in the future.

Yet, there was a number of problems with providing such feedback:

1) Today's world isn't static. It's dynamic and changes every day - at an increasing pace. To respond to changes, development goals and priorities need to be flexible - and what might have looked like a promising idea for a new feature yesterday may already have become irrelevant tomorrow. I need the flexibility to shift priorities and goals quickly if necessary to still be in business tomorrow.

2) It raises expectations. Even if I just say that I put an idea on the todo list, most people will expect it to arrive in a release coming soon (or very, very soon). Some people (even those who haven't asked the question themselves and just read about it) can become very brisk and insulting if "their" feature takes too long to implement in their eyes - or if it had to be removed from the todo list because of recent developments (=> see 1). This has taken the form of personal insults, slander and bad reviews with the intention to hurt the product and my reputation in the past.

That's why I usually no longer share any information in advance or provide any direct feedback related to future features or products unless a release with a completed implementation of a certain feature is imminent. Over the past years, this has worked far better than my previous, more open approach.

That said, again, thanks for your feedback. I'm just sorry I can't return the favor and give you mine.

Best regards, 
Felix Schwarz