If we have a beta we will make it public and let our users know about it. But we cannot share each and every step of the development process. Each company decides how much transparency it should provide and we don't believe that being that transparent necessarily speeds up the development process. We would rather spend this time and effort on the development itself.
Sorry, we didn't count how many customers we lost. That would be a useless exercise, given how much work to do we have ahead. We strive to fulfill as many promises as we can but it's not always possible to fulfill them all within a reasonable time frame.
We understand how important the Viewer for Mac can be for some users. The work on it is in progress now. Unfortunately, we couldn't provide it earlier simply because there were other priorities - features we needed to implement to increase our paid customer base. It's not that we don't want to or cannot implement all suggestions that we receive, it's only that we work on priorities because we must think about our bottom line. It's as simple as that.
Perhaps I should have explained my advice. Remote Utilities is software of dual nature. With each update, even a minor and sub-minor update there are little features and fixes added to Host and Viewer.
Therefore it doesn't make sense to troubleshoot a problem before Viewer version matches the Host version. Even more so - both should be the current version.
Otherwise, i.e. if we try to diagnose a problem when there is a version mismatch and/or it's an old version, we cannot tell if this is a yet unknown problem, or just an old bug already fixed in the current version.