Actually, no, I've offered some very specific observations, and one of them has apparently been acted on already.
"Rewrite it" isn't very specific.
The fact that JRiver responded to your one specific request shows that they will, when details are provided. But you have now caused yet another way to shuffle to be added to MC.
You don't get all the functionality without the complexity, simply because you need the options to select the functionality.
You don't get the responsiveness without duplication of methods to access functionality, when an App is developed in the way MC is. Also not everyone likes the same settings and methods to do stuff, so there will be duplication.
But I have said similar things to you in the past, and Jim has challenged me to be specific, make suggestions, and so on. I do what I can, because it isn't my day job, but I can't say that I have met that challenge. I'm also not a software designer. Maybe one day...
Bottom line, MC is cheap because it is a small development team. Because of that, if JRiver was to rewrite that whole interface, you wouldn't see any new functionality, or hear from the team, for six years. I prefer the complexity, continuous updates, and improvements to waiting for a long time to see what they may come up with.
Honestly, I think the way MC Standard and Theatre views present is due to the business model that JRiver uses, which is successful and has been working for a long time. Small team. Incremental and continuous development. Low price.
...But I would still like JRemote for Android to be brought up to equivalency with JRemote for iOS, which requires no suggestions because the model already exists. Plus more useability in Panel. But that is the challenge I have; to make suggestions on how.