3 ms·

It's very limited to think that the user experience comes before everything. If I focus purely on the user and not my business I don't have a business. If I do

It's very limited to think that the user experience comes before everything. If I focus purely on the user and not my business I don't have a business. If I do something good for the user experience but in fact breaks the law, then I am no longer in business. The user is incredibly important, but it's all a balancing act of resources and where to dedicate them.

kerkeslager 6y ago
If your business doesn't serve its users, I am not particularly concerned that you don't have a business. Its my impression that most relevant laws are geared toward protecting users from businesses, but I'd be open to hearing if you know of any exceptions (GDPR isn't one--secretly collecting data on users without their consent isn't serving users, it's harming users).
- tashoecraft 6y ago
  User experience is a broad term. People here generally think of speed, but in fact that can actually result in a worse user experience. I believe users react better to a loader that takes longer for certain tasks like calculating tax returns because they like to think the computer worked hard to get the best result. It’s not always black and white. I have had to implement features that are awful for the users, but are required by law to have. Others to protect the business from liability. I’m not saying doesn’t serve users as the original comment was “user experience” and was specifically mentioning JavaScript in terms of a presumably slow site. User experience is many things and all of them need to be considered. I totally agree that sites have gotten way to bloated, but the js community is recognizing that and trying to work on it, lazy loading and improvements to module bundling are going to help. I think the craze of tiny packages is coming to an end. Libraries post proudly when they have zero dependencies. As the community evolves it’ll improve, though some sites will probably continue to get worse as higher ups demand more features.
  - marvy 6y ago
    > awful for the users, but are required by law I am really curious what sort of law does this. (Though maybe I'm better off not knowing...?)
  - kerkeslager 6y ago
    > I believe users react better to a loader that takes longer for certain tasks like calculating tax returns because they like to think the computer worked hard to get the best result. It’s not always black and white. This is a concern with creating the impression that you're serving the user, rather than actually serving the user. > I have had to implement features that are awful for the users, but are required by law to have. Others to protect the business from liability. This is basically what you said in the previous post, and remains lacking in concrete examples.

kerkeslager 6y ago

If your business doesn't serve its users, I am not particularly concerned that you don't have a business. Its my impression that most relevant laws are geared toward protecting users from businesses, but I'd be open to hearing if you know of any exceptions (GDPR isn't one--secretly collecting data on users without their consent isn't serving users, it's harming users).

tashoecraft 6y ago
User experience is a broad term. People here generally think of speed, but in fact that can actually result in a worse user experience. I believe users react better to a loader that takes longer for certain tasks like calculating tax returns because they like to think the computer worked hard to get the best result. It’s not always black and white. I have had to implement features that are awful for the users, but are required by law to have. Others to protect the business from liability. I’m not saying doesn’t serve users as the original comment was “user experience” and was specifically mentioning JavaScript in terms of a presumably slow site. User experience is many things and all of them need to be considered. I totally agree that sites have gotten way to bloated, but the js community is recognizing that and trying to work on it, lazy loading and improvements to module bundling are going to help. I think the craze of tiny packages is coming to an end. Libraries post proudly when they have zero dependencies. As the community evolves it’ll improve, though some sites will probably continue to get worse as higher ups demand more features.
- marvy 6y ago
  > awful for the users, but are required by law I am really curious what sort of law does this. (Though maybe I'm better off not knowing...?)
- kerkeslager 6y ago
  > I believe users react better to a loader that takes longer for certain tasks like calculating tax returns because they like to think the computer worked hard to get the best result. It’s not always black and white. This is a concern with creating the impression that you're serving the user, rather than actually serving the user. > I have had to implement features that are awful for the users, but are required by law to have. Others to protect the business from liability. This is basically what you said in the previous post, and remains lacking in concrete examples.