03-19-2019, 01:58 PM
(This post was last modified: 03-19-2019, 01:58 PM by danbrotherston.)
When is the last time you complained about not seeing all the minutia behind your banking transactions, or felt that there was no transparency on where your money was going? Trust me, you're not seeing all the details.
I'm not suggesting doing the things you claim I'm suggesting--and this is the second time I have explained that. In fact, the current design does the things you say would be bad, it hides that relevant information through obscurity and broken design. The presto interface is the best example, I can never see how much money something cost me. But on the GRT design, I still cannot see how the amount column affects my balance.
I'm suggesting designing the interface so that it shows information relevant to the model the user has. That means by definition, if the information is important to the user, it is shown, if it isn't it's hidden, and the information is presented in a way that is consistent with how the user understands the system. That is *NOT* the case that is happening now.
I'm not suggesting doing the things you claim I'm suggesting--and this is the second time I have explained that. In fact, the current design does the things you say would be bad, it hides that relevant information through obscurity and broken design. The presto interface is the best example, I can never see how much money something cost me. But on the GRT design, I still cannot see how the amount column affects my balance.
I'm suggesting designing the interface so that it shows information relevant to the model the user has. That means by definition, if the information is important to the user, it is shown, if it isn't it's hidden, and the information is presented in a way that is consistent with how the user understands the system. That is *NOT* the case that is happening now.