A good plugin should be designed to provide ease of use along with the ability to really emphasize what are the important things for that given plugin.
Airwindows plugins, are at the opposite extreme, they do very little, but they do it very well (maybe a few more aids for setting parameters would help).
I give an example to better explain what I think should be kept in mind when designing the interface of a plugin: when you use a parametric equalizer, instead of having a thousand graphs, it would be better to have a button to listen to exactly the single band you are setting ... Seeing helps, but listening much more. Also the "see" should show what you really need to set the parameters and nothing else.
Calf in his MultiBand compressor does that, in a really straightforward way that even a dummy understands: it combines seeing and listening for what you are doing.
I use and appreciate LSP. However, when I open an LSP plugin, in addition to being amazed both by the graphical interface, which I like but also by the great complexity, I wonder if all that stuff is really necessary for making music. In fact, I often take it out and go back to the Calf plugins .
Linux OS: Manjaro
Intruments: Yamaha MODX8; Korg Nautilus; Yamaha Tyros 3, Akai Force, Korg ModWave, Upright bass, Electric bass
Audio Card: MOTU M4
Monitors: Yamaha HS8, Auratone, M-Audio BX5, PreSonus Eris E3.5
Engineer and Musician