My main point is that the people who have trouble with the complexities of a tool will have a more likely chance of abandoning the tool or switching to a different tool than learning. The people who can navigate the interface probably aren’t getting dumber for using the simpler interface either.
Specifically regarding this, I think what the poster is implying is that all of the options within a piece of software have been removed. The interface has been dumbed down until you can only do the exact couple tasks the team has designed it to do to, and nothing more. The options that allow us to fine tune the software operation to our needs, to flexibly use the tool have been removed to the point where all you get is a button to do the task, and if it fails you get a cute cartoon that says "omg, sorry!".
When using technology that hasn't been dumbed down, the development team can often be surprised at what users are doing with it, because they are doing all kinds of things we never thought of. Once the software has been dumbed down enough thats not possible, because the software wont let you do anything the development team didn't think of.
This is exactly what I (and some colleagues) observe in academia, we now have first semesters that have grown up with smartphones and tablets but have never used "a computer" before.
That leads to some awkward conversations:
- "can you send me your file?" student: "but I only have that in word?" - "yes ... can you send it to me?" ... " student: "but I only have that in word!" - "... ?"
My prediction / fear is that this will only get worse over time as we have not hit the first generations that have been born after widespread touchscreen adoption yet.
Speaking of school, I'm in the age group you mention, and I'm baffled how those people have managed to get to University without knowing the concept of a file. Almost every paper I've written since the beginning of high school has been turned in as a PDF in Turnitin or Google Classroom.
It seems more likely to me in general that 'making technology more accessible increases the number of people who will be able to access that technology' than 'simpler interfaces make people dumber'.
The thing that I find bothersome is the expectation of simplified interfaces and feature sets outside of professional domains. It is an approach that works well if the software does exactly what you want of it, yet fails miserably the moment a user's expectations deviates from the developer's expectations. There is little room for creative thought or problem solving since the software tries to do everything for the user rather than providing a set of tools to them.
I think enough during my workday. And when explaining things to my daughter or reading a book.
You probably never read the book, because the author never tells you to "dumb things down" but to make them so intuitive you don't have to think about them.
Same way you don't have to think how to open a tab or a door.
Have you ever been in front of a door and wondered if you had to push, pull, approach, slide? That's bad design.
Bunz's conclusion: "The difference between empowering the user and manipulating her or him is minimal, but decisive: it makes a difference whether the interface is empowering you, or patronizing you while hiding it in bright, friendly colours and the technique of infantilization. In a conversation about this contemporary problem of interface designs, Robert Ochshorn (2014) pointed out that there is, indeed, a fine line between ‘designing to empower a skilled user’ and ‘designing to prevent a user from feeling stupid’. This means that the difference between the interface assuming you are intelligent and teaching you to outgrow it, and patronizing the user by eliminating the possibility of making mistakes while effectively controlling her or him, is difficult to spot. Following Wendy Chun, who addresses the new media of today as a habit, one can say that habits ‘are both inflexible and creative’ (Chun 10.1057/9781137437204 - Postdigital Aesthetics, Edited by David M. Berry and Michael Dieter200 Infantilization in Digital Environments forthcoming 2015; Chun 2015, this volume), while Tiziana Terranova (2004, 83) has pointed out that online spaces cannot be conceived as ‘purely functional’. As I have pointed out elsewhere (Bunz 2014, 50), this is a tendency we find often when looking at the being of technology: technology is haunted by an ambivalence – in this case, its potential to manipulate and its potential to empower people. Despite infantilization looking friendly and innocent, it might follow other interests, and, at a time in which computers are becoming ubiquitous, we need to be aware of this. Soon, infantilization might leave our screens to be found on the things around us – Google has recently launched a car with a smiling face. Being addressed as a child is ambivalent, and this ambivalence is typical of our time: technology companies want people to feel comfortable and play with their technology. At the same time, people also need to take technology into their own hands, as learning how to use it not only empowers them, but also shapes what technology becomes: school will never end."
[Edit: Seems obvious companies try their best to make products that get people consuming more instead of producing more. Removing complexity from digital interfaces is a recurrent theme.]
About TFA, I believe everything has its place - open source shouldn't try to "win" and just do its thing. At the same time megacorporations devote greater and greater resources to bigger projects like the linux kernel.
This is not an indictement though... software is getting more complex and i.e. it's unthinkable now for anything but a very large company to make their own browser.
I don't know where we go from here.
software is getting more complex and i.e. it's unthinkable now for anything but a very large company to make their own browser.
isnt the answer then to reduce the incidental complexity?provide alternatives that have "onramps" to greater capability instead of being stuck in "dumb ui land".
even a browser could be re-imagined as just a vm that runs "html" as a shared lib for one type of content, greatly simplifying the model for broswer makers
there are lots of potentialities i think
AI's are now in the early stages of being used to write code and that's only going to increase.
This was prescient (article is from 2015) of the media kindergarten of the past 5 years