For managing permanent properties, I think mechanical interfaces are the best option, though of course vastly more costly.
Any control interface is by definition acting on something dynamic, so even pushing a physical button, we expect the some status to reflect the result instantly.
I think touchscreen could be best used as a step above joysticks, when an action cannot just be summed by a on/off (or +/-) state, or a vector in one direction.
Imagine in a military setting if you need to open a communication channel with 4 teams moving close to each other to warn them of a nearby enemy. Would you prefer to switch the “open communication” lever, check the team numbers, push the buttons 1, 5, 6, 12 and the “open channel” button. Or circle them directly on the map and click “open communication” on the right side panel?
I also think that a lot of touchscreen interface are immature and ill thought, but it would be the same issue with stupid buttons like we can find in so many cars for instance (why would the parking brake switch be next to the A/C on/off ?)
> inherently inferior / single-system
From the top of my head, maps work better on touchscreens. Navigating document trees. Making elements link together, group them. And there must be hundreds of uses not obvious now because we haven’t tried enough.
Actually I don’t see how any input system would not have some high-stake single system where it’s a perfect fit. That would just be failure of imagination in my opinion.