2 ms·
There is a solution, but at this point, I think no vendor has the guts to apply it. The solution is: 1) Publish Human Interface Guidelines that detail a rich
by TeMPOraL 6y ago
There is a solution, but at this point, I think no vendor has the guts to apply it.
The solution is:
1) Publish Human Interface Guidelines that detail a rich set of standard gestures, how various tappable elements MUST be marked, and how they SHOULD be arranged.
2) Publish abridged HIG for end-users as a part of user manual for the device/platform. Aim for closed-world reasoning, i.e. the user must be able to build a mental model of, "if I can't see this functionality here, here or here, it does not exist", and not "it may be hidden somewhere else".
3) Tell app developers to stick to the HIG or GTFO.
I know, wishful thinking.
The decay started long, long ago. The other day, someone commented on HN with a link to a piece of old Microsoft WinAPI documentation, I think Windows 95 era or older, where there was a side note on window styling and "escape hatches" that unfortunately had to be built in, because marketers are marketers and desperately want to fuck up usability to put branding on things. Back then, platforms already gave away too much control over styling to software vendors (where originally this control resided with end-user).
- marcosdumay 6y agoYou know, by the Win 95 era the GUI toolkits would take descriptive code informing what kinds of interactions you can have, and automatically add the correct markings and widgets. It's interesting that nowadays, with all the work gone into sandboxes and frameworks, nobody seems able to do that.
- TeMPOraL 6y agoNobody cares to do that. Declarative UIs, where you describe what is being represented and what can be done with it, and the framework styles it up for you - these are desirable by developers and users, but not by people holding the money to pay for development.