Could not agree more. Reminds me of my last job, where IT had to create a Wiki just to explain how to use our "productivity" suite (Agile), the use of which was not optional.In the UI industry we have saying:
"UI is like a joke. If you have to explain it, it doesn't work"
If reading the manual is necessary to operate a UI, then the UI has failed as an interface between the human user and the software.
I used Zebra for years before consulting the manual and it wasn't to understand how the UI works, but rather obscure stuff like the oscillator effects. I don't think I've ever read (back to back) the manual of any software.
I'm hoping the ultimate explanation will come down to the sheer flexibility requiring such an opaque interface.
Here's a thought: what Falcon needs is a 'wrapper'. Nah. I'm not holding my breath.