SOTE wrote: ↑20 Jan 2022, 08:24
For your first post on the forum, that looks pretty vicious
First post after a first really bad experience. If I praised the application I would be a liar, and if I felt happy and grateful after struggling all day long to no avail, then I'd be a robot.
SOTE wrote: ↑20 Jan 2022, 08:24
and a bit self-centered, aka "make it completely useless for me".
Should I have talked about you then, or about everyone, when I was describing my own experience and the way I perceived it?
SOTE wrote: ↑20 Jan 2022, 08:24
something I've noticed over the years, when people use new software they tend to blame any initial failures on it versus themselves.
I wish that was true, but it’s not, the vast majority of people tend to
blame themselves instead, subconsciously, and feel bad about themselves, like they are incapable to make a simple piece of software or hardware work.
Those who do blame it, and don’t fall to that self-deception trap, are only the few who have a lot of experience with software and understand usability principles. And they rightfully do so. Software must be human-friendly, first and foremost.
It's the software that has to adapt more to humans, not the other way around. I'd say 99% software to humans adaptation and 1% humans to software at most, because it's a matter of efficiency: 1 or 10 developers’ adaptation to human nature, vs thousands to tens of millions of people adaptation to bad software. It’s impact to the increased cost of life is enormous and highly underestimated.
So something I've noticed over the years, is that developers (software or hardware ones) are the only ones to blame, always.***
This view is also aligned with the marketing perspective i.e that
"the customer is always right even when you are most definitely sure that they are not". I develop hardware and software, so I see things from the developer’s point of view too.
SOTE wrote: ↑20 Jan 2022, 08:24
not bothering to read instructions, do tutorials, or examine examples.
You can't blame them, life is too short, and spare time is limited to non-existent. They follow their instinct, and they are right: contrary to the common devs' belief, all of an app’s functionality can be made self-explanatory and intuitive, with no need to read any manuals at all.
Reading should be optional, and if some user-training is necessary, it should be embedded seamlessly on the interface. That’s what we should aim for, because it’s perfectly feasible, and it’s the future.
The fact that it is considered very hard, or even impossible today, is because the vast majority of developers place usability as their last priority. Usability is a science and technology that needs to be evolved like everything else, as it is affecting our lives more than we think, and even affects tech and science evolution itself, significantly.
In other words, when it is obvious to the user that something simple should work, it should work, period.
***In my case, I watched two tutorials, and found out the next day that there was a workaround mentioned on the forum (but not on the tutorial) that eventually made it work (the Variations value). That simply means bugs, under-development, and bad usability, not user-fault. I know because I make such bugs myself, but I always struggle to resolve them and improve the functionality and overall quality of the software before I publish it, even when I make something (eg a tool) exclusively for myself -just to keep the good habit.
SOTE wrote: ↑20 Jan 2022, 08:24
when asking for help, being considerate and respectful to the creator of the software is the least one can do.
When did I ask for help? I didn’t, because I had decided to look elsewhere, so I just provided my honest critical feedback as a user who tried the software, but while searching for other software, I stumbled upon an image search discussion in the search results, and found the workaround.
Second, respect is earned, not granted. That allows the developer who invests in providing a smoother experience to earn more respect than the one who's causing a lot of suffering, and promote quality vs sloppiness.
SOTE wrote: ↑20 Jan 2022, 08:24
Nobody is forcing you to use it.
Nobody is forcing you to accept my critical feedback either, yet you decided to counter it .
It all comes down to the “Free” fallacy. The users must adapt and be grateful too, just because the software is given to them "for free".
Nothing is “free” on this world, especially the users' precious time that they invest on adapting to poorly made software -not to mention the effort, the psychological impact, etc. All software should be treated with the same high standards, both by the developers and the users, whether it is free of charge, or paid. Period.
I'm not claiming that this app is trash, quite the opposite, but it has some poorly made functions. Just one of them costed me a whole day of struggle, that's how damn important bug-resolving and usability is, and that's my point.