I'm not sure I completely agree with the author regarding the paradigm shift from viewing to editing in the same place. I think these are two very different activities, and in my opinion, this should be reflected in the UI.
However, I myself apply the ideas presented here when it comes to ‘expanding’ the data displayed by a card with a certain degree of conciseness.
I really liked the idea of displaying the extended data in a panel with a slightly different background color, especially when it comes to parent-child information.
Other readers have pointed out that when this extra information is very long, the system can become a problem. And yes, it is a problem. In these cases, if my experience is of any use, I add a pagination buttons at the base of the accordion..
This is great. However, this depends on context. If the avg frequency of users version history is 40+ or larger number, the accordion style would be problematic as interaction cost and cognitive effort would be increased. In that scenario I believe, a modal could be used with essential info abstracted for cognitive continuity and context loss prevention.
This is inspiring stuff. I can absolutely see the potential for keeping current and historical data organized in the same way, and visible together. I’ll refer to this article the next time a developer tells me we’ll just show everything in a modal. 😄
I'm not sure I completely agree with the author regarding the paradigm shift from viewing to editing in the same place. I think these are two very different activities, and in my opinion, this should be reflected in the UI.
However, I myself apply the ideas presented here when it comes to ‘expanding’ the data displayed by a card with a certain degree of conciseness.
I really liked the idea of displaying the extended data in a panel with a slightly different background color, especially when it comes to parent-child information.
Other readers have pointed out that when this extra information is very long, the system can become a problem. And yes, it is a problem. In these cases, if my experience is of any use, I add a pagination buttons at the base of the accordion..
This is great. However, this depends on context. If the avg frequency of users version history is 40+ or larger number, the accordion style would be problematic as interaction cost and cognitive effort would be increased. In that scenario I believe, a modal could be used with essential info abstracted for cognitive continuity and context loss prevention.
This is inspiring stuff. I can absolutely see the potential for keeping current and historical data organized in the same way, and visible together. I’ll refer to this article the next time a developer tells me we’ll just show everything in a modal. 😄
Good stuff!