|
|
|
|
|
by balder1991
287 days ago
|
|
For the vast majority of people, including professionals like doctors, a computer or an OS is not a subject of interest, it's a tool, and they want it to be as invisible and reliable as the electricity that powers it. The moment the tool demands attention—be it through an error message, a confusing interface, or an unexplained requirement—it stops being a tool and becomes an obstacle that creates frustration, anxiety, and outright hatred. The average user doesn't want (and shouldn't need) to understand technical stuff like file formats (JPEG vs. PNG), the data load of video streaming, what a "driver" is, etc. Forcing them to grapple with these concepts is a fundamental design failure, but I think it’s a difficult pill to swallow for nerds to accept that others just don’t care about these things. This is why companies like Apple have been so successful: they don't just simplify the interface, they abstract away the complex, technical reality into a language and experience that feels intuitive and friendly for the users. |
|
[EDIT] The core problem, in case the example didn't make it clear, is that these things interrupt a workflow they use often, and are accustomed to having always work the same way, and do so in service, usually, of showing them a bunch of stuff they don't give a fuck about and didn't really need to know. Even the ones that block interaction to highlight new features are really bad—OK, that's nice, but I'm trying to do the thing I always do with this and you're getting in my way, making my program temporarily behave and look weird and confusing, et c.