I don't think we've said that.
Not trying to put words in your mouth or attribute an exact quote, but it seems to me the approach is to focus on the core. I'm not implying that's a bad thing, that is in fact what brought me to JRiver.
We've spent a lot of time on network features. Remotes are just one of those.I think there are five or six. We've done Gizmo, Panel, and part of JRemote. MC itself makes a good remote.
I was referring to the three non-desktop apps I could think of that were community developed (JRemote, MO4Media, and EOS). I don't really think of Panel as an app. It doesn't stand on its own, it requires a web browser to launch. So while it might run on a different platform, it's not a natural feel on that platform. It feels like a webpage.
My point to add onto Mark's post is illustrated with this: In the near future I'll be redesigning my living room. There will be a Roku, or a Roku enabled TV, (because that gets me Netflix, YTTv, ec), but not a full blown HTPC. I don't think I'm alone in that future. I'll figure it out, and perhaps I'll use something else. I will certainly still use MC for other things, but the ecosystem is less valuable as I start to use other media software.
I don't want you to drop development work on MC24 to support more platforms (maybe Mark does, so not speaking for him). But I do wish there was more support for these types of devices. With what I know from MC, that support will likely come from community development and I appreciate that JRiver enables that.