things humans are bad at: memorising specific sequences of words
-
-
-
@kirtai @bri7 @oblomov @apophis That being said, there's a limit to expressivity of features that can be had without some degree of user-internalized model of operations.
At some point actually explaining all the things at once becomes sensory overload and explaining them separately in sequence becomes in itself overwhelming or overly tedious.
Dynamic systems have a much easier time of things here for obvious reasons, but user model & skill has to develop at some point for some things. -
@kirtai @bri7 @oblomov @apophis That being said, there's a limit to expressivity of features that can be had without some degree of user-internalized model of operations.
At some point actually explaining all the things at once becomes sensory overload and explaining them separately in sequence becomes in itself overwhelming or overly tedious.
Dynamic systems have a much easier time of things here for obvious reasons, but user model & skill has to develop at some point for some things. -
@bri7 @lispi314 @oblomov @apophis
Actually here they are.- Rigel's Revenge: Text adventure: Required the exact phrase "introduce bomb".
- The Price of Magik: Text adventure: Required the exact phrase "Bat, take wheel". Get does not work here despite being a synonym of "take" for the entire rest of the game.
- Beneath a Steel Sky: Point and click: Required you to notice a single pixel lightswitch in a textured background in order to pass one of the last rooms in the game.
It's been, what, thirty years since I even looked at any of these and I still remember them with annoyance.
-
@bri7 @lispi314 @oblomov @apophis
Actually here they are.- Rigel's Revenge: Text adventure: Required the exact phrase "introduce bomb".
- The Price of Magik: Text adventure: Required the exact phrase "Bat, take wheel". Get does not work here despite being a synonym of "take" for the entire rest of the game.
- Beneath a Steel Sky: Point and click: Required you to notice a single pixel lightswitch in a textured background in order to pass one of the last rooms in the game.
It's been, what, thirty years since I even looked at any of these and I still remember them with annoyance.
-
@kirtai@tech.lgbt @bri7@social.treehouse.systems @oblomov@sociale.network @apophis@yourwalls.today Regarding the following:
show users the list of possibilities, as objects that suggest visibly what their function is.
let people interact directly with those objects.
which-key-mode (github) kinda does that, it even has full mouse-over description without requiring configuration and click interaction.
It isn't enabled by default but I think that this suggestion might address that.
It's a bit unfortunate it took this long for these to come into existence (they are not perfect, and some limitations in rendering cannot be fixed without something like this), but they have.
-
@bri7 @lispi314 @oblomov @apophis
Actually here they are.- Rigel's Revenge: Text adventure: Required the exact phrase "introduce bomb".
- The Price of Magik: Text adventure: Required the exact phrase "Bat, take wheel". Get does not work here despite being a synonym of "take" for the entire rest of the game.
- Beneath a Steel Sky: Point and click: Required you to notice a single pixel lightswitch in a textured background in order to pass one of the last rooms in the game.
It's been, what, thirty years since I even looked at any of these and I still remember them with annoyance.
@kirtai @bri7 @lispi314 @apophis I remember pixel hunting being the bane of some classic LucasArts game too! Compounded by the need to use a specific Look command to do it, too.
And I remember Heart of the Alien (sequel to Another World/Out of this World), a platformer, also had a bomb placement that require a specific sequence of movement keys to do. Reading the manual was the only way to know.
(“bat, take the wheel” is a specific idiomatic expressions, I'll allow it.)
-
@kirtai @bri7 @oblomov @apophis That being said, there's a limit to expressivity of features that can be had without some degree of user-internalized model of operations.
At some point actually explaining all the things at once becomes sensory overload and explaining them separately in sequence becomes in itself overwhelming or overly tedious.
Dynamic systems have a much easier time of things here for obvious reasons, but user model & skill has to develop at some point for some things.@lispi314 @bri7 @kirtai @apophis
this is true for any physical tool as well. Even a hammer requires learning to use correctly. There's a trope that claims that the only intuitive interface is that tit, and even THAT is wrong, as anyone who has experienced motherhood knows: babies do not, in fact, latch and start suckling automatically. It's just that mothers* generally** make all efforts to ensure that that baby learns within the first hours
1/n
*usually
**not always, sadly -
@lispi314 @bri7 @kirtai @apophis
this is true for any physical tool as well. Even a hammer requires learning to use correctly. There's a trope that claims that the only intuitive interface is that tit, and even THAT is wrong, as anyone who has experienced motherhood knows: babies do not, in fact, latch and start suckling automatically. It's just that mothers* generally** make all efforts to ensure that that baby learns within the first hours
1/n
*usually
**not always, sadly@lispi314 @bri7 @kirtai @apophis
2/n
because it's essential for the baby's survival.
The idea that this can be magically avoided on a computer is preposterous.
Microsoft has inveted decades of UX research to make the UI of Word as accessible as possible and the best they could come up is the Ribbon interface, which is a clusterfuck of sensory overload where nothing is where you would expect it to be *unless you already have a mental model of where things should be*.
-
@lispi314 @bri7 @kirtai @apophis
2/n
because it's essential for the baby's survival.
The idea that this can be magically avoided on a computer is preposterous.
Microsoft has inveted decades of UX research to make the UI of Word as accessible as possible and the best they could come up is the Ribbon interface, which is a clusterfuck of sensory overload where nothing is where you would expect it to be *unless you already have a mental model of where things should be*.
@lispi314 @bri7 @kirtai @apophis
3/n
The net result is that SOME things are where SOME people expect it, but nothing is where everyone would expect it and no one will find all things “automagically”.
And people still do centering by adding “an adequate number of spaces in front of the text” as if they were working with a typewriter. Even among the younger generation that have never seen a typewriter in their life.
-
@lispi314 @bri7 @kirtai @apophis
3/n
The net result is that SOME things are where SOME people expect it, but nothing is where everyone would expect it and no one will find all things “automagically”.
And people still do centering by adding “an adequate number of spaces in front of the text” as if they were working with a typewriter. Even among the younger generation that have never seen a typewriter in their life.
@lispi314 @bri7 @kirtai @apophis
4/n
(Heck, I still remember when they tried to make progressive discovery a thing, by hiding less common menu entries by default, with the only result that they broke everybody's muscle memory. Meanwhile, WordPerfect had had a sensible menu system for *years* and even less tech inclined people could find anything they needed simply because it had a more accessible model through and through.)
-
@lispi314 @bri7 @kirtai @apophis
4/n
(Heck, I still remember when they tried to make progressive discovery a thing, by hiding less common menu entries by default, with the only result that they broke everybody's muscle memory. Meanwhile, WordPerfect had had a sensible menu system for *years* and even less tech inclined people could find anything they needed simply because it had a more accessible model through and through.)
@lispi314 @bri7 @kirtai @apophis
5/n
And by the way, we do not have ridiculous amounts of screen estate compared to the old days. Even if most people at a computer (i.e. not using a tablet) will have a larger monitor than the 12" or 13" of lore, they still rarely have more than a 16", and the higher resolution is better used for crispter text at the same visual size than to cram more information on screen.
-
@lispi314 @bri7 @kirtai @apophis
4/n
(Heck, I still remember when they tried to make progressive discovery a thing, by hiding less common menu entries by default, with the only result that they broke everybody's muscle memory. Meanwhile, WordPerfect had had a sensible menu system for *years* and even less tech inclined people could find anything they needed simply because it had a more accessible model through and through.)
@oblomov @lispi314 @kirtai @apophis just because they spent money on it doesn’t mean they listened to the people they spent money on, nor that those people knew what they were doing.
there are better and worse designs for ui. there are measurable principles. that we have a lot of bad examples doesn’t imply tgat good , discoverable ui doesn’t or can’t exist
but, ecen the best designs (which microsoft has never produced), has some learning curve.
-
@lispi314 @bri7 @kirtai @apophis
5/n
And by the way, we do not have ridiculous amounts of screen estate compared to the old days. Even if most people at a computer (i.e. not using a tablet) will have a larger monitor than the 12" or 13" of lore, they still rarely have more than a 16", and the higher resolution is better used for crispter text at the same visual size than to cram more information on screen.
@lispi314 @bri7 @kirtai @apophis
6/n
So at some point one still needs to RTFM (or more in general actually learn how to use the tool). The best UI is not something that makes everything accessible at once (it's simply not possible beyond a certain size of the feature set), it's something that makes it trivial to use common features, and guides you in the discovery/learning of the less common ones. And a good documentation and menu system is what does this.
-
@lispi314 @bri7 @kirtai @apophis
5/n
And by the way, we do not have ridiculous amounts of screen estate compared to the old days. Even if most people at a computer (i.e. not using a tablet) will have a larger monitor than the 12" or 13" of lore, they still rarely have more than a 16", and the higher resolution is better used for crispter text at the same visual size than to cram more information on screen.
@oblomov @lispi314 @kirtai @apophis we’re still looking at documentation on the aame screen as the software we are using. it’s not like we are laboring ubder the constraint that we physically cannot do that cos we do all the time.
what ai am suggesting is we can take it a step further by making the ui self documented- don’t make the document a separate artefact from the ui. combine them.
-
@lispi314 @bri7 @kirtai @apophis
6/n
So at some point one still needs to RTFM (or more in general actually learn how to use the tool). The best UI is not something that makes everything accessible at once (it's simply not possible beyond a certain size of the feature set), it's something that makes it trivial to use common features, and guides you in the discovery/learning of the less common ones. And a good documentation and menu system is what does this.
@lispi314 @bri7 @kirtai @apophis
7/7
There's two examples that come to mind: one is the orthodox file manager (Norton Commander & friends), and the other is the menu system that I only ever found in one desktop program and I can't even remember which, that came with a search function. So you had a SEARCH interface that allowed you to LEARN where things were, and if you were a frequent user of that less common feature you would subsequently just use the menu to find it (muscle memory).
-
@oblomov @lispi314 @kirtai @apophis just because they spent money on it doesn’t mean they listened to the people they spent money on, nor that those people knew what they were doing.
there are better and worse designs for ui. there are measurable principles. that we have a lot of bad examples doesn’t imply tgat good , discoverable ui doesn’t or can’t exist
but, ecen the best designs (which microsoft has never produced), has some learning curve.
-
@oblomov @lispi314 @kirtai @apophis we’re still looking at documentation on the aame screen as the software we are using. it’s not like we are laboring ubder the constraint that we physically cannot do that cos we do all the time.
what ai am suggesting is we can take it a step further by making the ui self documented- don’t make the document a separate artefact from the ui. combine them.
@bri7 @lispi314 @kirtai @apophis
In
https://sociale.network/@oblomov/116096244460698938 I provide an example of the best self-documenting interface I remember (can't say “I know of” because I can't remember which program had it). -
@oblomov @lispi314 @kirtai @apophis we’re still looking at documentation on the aame screen as the software we are using. it’s not like we are laboring ubder the constraint that we physically cannot do that cos we do all the time.
what ai am suggesting is we can take it a step further by making the ui self documented- don’t make the document a separate artefact from the ui. combine them.