4 ms·
At what point do you stop blaming the user and start blaming the designer? Who's fault is it if a user doesn't know how to use a mouse and keyboard? Should we e
by xmprt 7y ago
At what point do you stop blaming the user and start blaming the designer? Who's fault is it if a user doesn't know how to use a mouse and keyboard? Should we expect all apps to be built with text to speech and touch input as the primary interface? That just seems like a UX nightmare to me.
To apply that extreme to this case, I think it's not too much to ask that users know what the start menu is and how to use it to find and start apps.
- c3534l 7y ago> I think it's not too much to ask that users know what the start menu is and how to use it to find and start apps. It is when you provide icons for most applications, but only provide text search for others (which has a confusing interface that sometimes displays webpages and local documents). There are limits to blaming the designer, but inconsistent, half implemented, with few affordances, that uses mixed metaphores is neither good programming or good design. It's not always the fault of the design, but this design is the fault in this case.