User-Centric Software Design
The cluster centers on the debate over whether developers should design software tools to adapt to user expectations and behaviors for convenience, or expect users to learn and adapt to technical complexities.
Activity Over Time
Top Contributors
Keywords
Sample Comments
It's really sad that the tool you design should adapt to its users rather than its users having to adapt to your tools?
Perhaps the fundamental issue is your ignorance? Don't you know that users require tools that just work and that they should not be required to understand all of this technical nuance?
software should do what users expect it to do, not what developers think it should do.
Educating users? Users follow the path of least resistance. Make anything more complicated, and they will switch to something more convenient. Do you expect users to really be sensitive to the plight of devs?
As a UX/UI designer, this is entirely the wrong conclusion to make. Users come in all shapes and forms with different priorities, distractions and abilities. They are good at the things that matter to them.A common mistake software developers make is believing their software is important enough to warrant the investment in time it takes to learn it.It usually isn't.
Users don't want to design their user interface, it's not their job. This approach is like - here are some musical notes, compose the song that is perfect for you!
Users don't care about the code. They care about convenience.
Don't blame the end user for doing something you don't want them to do if it is more convenient to do and works without immediate consequences. Redesign it or rethink your assumptions.
Much more strange when a tool blames its users for their unsatisfying experiences. It is tool is made for user, not the other way.
Because tools should be built for their users, not the other way around.