ObDisclosure: I'm in the embedded/middleware space.
I dunno. My peers don't write UI much at all; I do these things as force multipliers for my own nefarious purposes.
None of it gets "published" in a formally supported way, so I don't have any accountability for 'em. They're intentionally ugly but not dissonantly so. The design is "look, but don't touch." I mainly use them to anticipate integration errors and do something useful to aid in diagnosis of those. The theme here is "it ain't me, babe" or "holy cow, thanks for finding that" - determination on that axis.
But I also put adequate instrumentation in to exploit in the first place. Seems to be a lost art.
To me, the perfect user interface is no user interface at all - maybe a "push to start" button - a physical button. Second best is command line/scripting, third is the sort of thing I write.
In the embedded space, you might get a perception that this is cheating. I just smile.
I dunno. My peers don't write UI much at all; I do these things as force multipliers for my own nefarious purposes.
None of it gets "published" in a formally supported way, so I don't have any accountability for 'em. They're intentionally ugly but not dissonantly so. The design is "look, but don't touch." I mainly use them to anticipate integration errors and do something useful to aid in diagnosis of those. The theme here is "it ain't me, babe" or "holy cow, thanks for finding that" - determination on that axis.
But I also put adequate instrumentation in to exploit in the first place. Seems to be a lost art.
To me, the perfect user interface is no user interface at all - maybe a "push to start" button - a physical button. Second best is command line/scripting, third is the sort of thing I write.
In the embedded space, you might get a perception that this is cheating. I just smile.