Hi. What you have to realize is that being "transparent" to you is being transparent to everyone - including our competition. So, that is one reason you are not going to see a lot of definite commitments on exactly what is under development at any given time or when things will be released. We usually will tell you when something is actively under development but may not be able to provide much information before then.
I get where you are coming from, but the thing is, it's going to happen one way or another. You aren't making a unique product here, so you can't expect that other competitors won't have the same functions and features as you, as there is nothing truly novel about what we are doing here. Apple constantly gets beaten to the punch on features by other phone manufacturers, yet you don't see them going out of business, or exiting the phone market because someone implemented fingerprint ID before they did. Among all the things Apple is known for, they do 2 things extremely well: First, they have excellent customer service and support. Second, they are smart enough to realize that there is a natural flow to the way people expect things to work, and they are very good at shaping their products to follow that flow. So when people point out something that doesn't make sense (like this), which is simple to fix (this is literally changing the order of a few lines of code, or alternatively, adding a flag to show that there are extras), it's frustrating to get rebuffed (see my first post above re: If the Emby Team disagrees with the user request)
As pir8radio pointed out earlier in this thread, if people really wanted to steal your features, they could look at your product, then look at the forums for what people are requesting, and implement the features themselves. What keeps them from doing this? Well, for major things, it's like you said earlier:
Very complex items that impact everything take much longer for us to be able to commit to - and, sometimes, even if the entire community wanted them, they may not make sense to implement just due to their cost or other impact on the system.
If you know that, your competition knows that as well, and either: 1. They won't do it either, hence not beating you to the market, or 2. They will spend WAY too much time working on that one thing, thus falling behind YOU, and surprise surprise, you still win.
The only thing keeping your users in the dark does is frustrate them, and cost you more time closing and merging redundant threads on here asking for the same thing. If we had some kind of roadmap to reference, we would at least know something is on the horizon, instead of going almost 2 years in a thread thinking it was on the horizon, before finding out it's not even under active developtment: For reference
There is no hard and fast number for a request and, while we want the feedback out here to gauge user interest in these features (and just give us ideas we haven't thought of), most times, there are a lot of other factors that have to be considered. One of the most common is complexity of implementation and how much of an impact it will have on the system overall. Very complex items that impact everything take much longer for us to be able to commit to - and, sometimes, even if the entire community wanted them, they may not make sense to implement just due to their cost or other impact on the system.
Let's be honest here, liking a post really does nothing when it comes to feature requests. Look through the first 5 pages of the feature request section and you'll see that the vast majority of posts that have over 10 "likes" are at or well over a year old, and have yet to be implemented. The highest upvoted feature request right now in the top 20 pages of this forum has 63 requests (not even counting how many similar threads may have been locked for being duplicates), and it's not even under active development at this time, despite being created by a developer (i.e. you) and being over 2.5 years old. If THAT feature request can't even get implemented, why would anyone bother to upvote anything, after seeing that go nowhere for 2.5 years? Despite this, your go-to response for users is still, "Liking the original post on these topics is the best thing to do."
As far as simple requests vs. complex ones, well, I already addressed the complex. For the simple ones, it goes down exactly how I described in my first post that started this thread. If the Emby team agrees with you, you might have a chance at getting it implemented (granted, it will be at some unknown date in the future, and maybe not even then). If they disagree, you get the script.
Also, this wasn't within the scope of your questions, but many times we see people pop into a three year old feature request with a comment like "its been 3 years why hasn't this been done yet". Well, when that comment is the first activity that item has had in 3 years, then that actually tells us that not many people are interested in it. That is just to say that the amount of time a request has existed is not a very good gauge for whether or not it should be implemented .
We value everyone's ideas and requests and do really try to react to them as best we can - along with keeping up with all the changes in technology we need to and the competition.
This is part of the "Transparency" I was talking about. As I explained earlier, this is more often than not because you guys give convoluted answers that leave people thinking things are getting worked on, when in fact they actually aren't. If I think something is being worked on, I'm not going to bug the developers about it and bump an old thread. Look at any one of those threads you are thinking about, and you will see the same pattern of a convoluted answer, no activity for a while while the users think it is getting worked on, then after a year somebody pops in and asks why it hasn't been implemented, cue another convoluted response, wash rinse repeat.
In addition to that, keep in mind that you have FAAAAR more server admins on these forums than you do just regular emby users. So while you may be speaking with only one admin, that one person could be representing 20 different users that are on their server asking for the same thing. I'm sure you guys have hard numbers on emby users vs. installed server instances, so it can't be hard to understand that you are dealing directly with only a tiny fraction of the people who actually interface with your service. It's like voting in the general election: How many people are registered vs. how many actually turn up at the polls. Just because you don't have 1,000 people beating down your door to get a feature request implemented (i.e. "liking" the post, or adding their commentary), doesn't mean that there aren't still 1,000 people out there that want the feature. Just like you have a huge number of users with only a small number of admins, you have the same thing within the admins themselves: Out of all the admins, there are only a fraction of those that are going to get on these forums and put in feature requests to begin with.
That is only one factor but, no, we're not crazy about being beaten to the market with features.
The reality is that, even if we wanted to be "completely transparent", I believe it would just cause more trouble than anything else. We are extremely agile in our plans and are constantly reacting to feedback and other influences to improve the system. This often means that things we plan even a month or so out, change. If we tried to publish this then, many, many times we would just miss expectations and make people even more upset. You usually know about new things once they hit the beta stage.
We can do a better job of selecting and prioritizing some of these feature requests, however, and we will strive to do that.
I'm not going to go back and reiterate, I think I've already responded to all the points in your first 2 paragraphs. I bolded that last line because it epitomizes everything I've been trying to explain throughout this post. I will end with this:
We appreciate what you guys are doing, and we thank you for doing it. I wouldn't be a premiere subscriber if I didn't like the vast majority of Emby, and want to help it improve and grow. That being said, things would go much smoother for both your users and yourselves if we had more information, and some realistic responses that didn't come off as completely canned while providing zero definitive information. I for one appreciate the dialogue we are having here, and you taking the time to respond. Thank you for listening and continuing to have a constructive discussion with me, so that maybe things can get better for everyone