2 ms·
I wonder if this is a consequence of the modern, "user-story-driven" style of UI development. I'd claim that, back then, when UI design was considered less imp
by xg15 10y ago
I wonder if this is a consequence of the modern, "user-story-driven" style of UI development.
I'd claim that, back then, when UI design was considered less important, most UIs were either essentially random - or organized around the manipulation of "virtual objects" that conveniently mapped to the underlying data structures. (Files and folders, emails, DB entities, ...)
Some of that resulted in you getting a sort of UI consistency "for free", simply because the data structure had to be consistent. So you'd offer the "natural" actions for an object to the user (mostly CRUD) without thinking much which use-cases these actions were fulfilling.
In contrast, modern UI design seems to be driven less by abstractions and more by a priority-ordered list of individual use-cases. One consequence of this is that certain features can be missing even though you'd reasonable expect then to be there - because the use-case wasn't decided to be important enough.