Re:The Distribution of Users’ Computer Skills: Worse Than Yo...
by kube-system on Monday September 23, 2019 @04:03PM
(#21052983)
I'd agree with you if we're just talking about business users, or even home users with high-educational attainment. But this article is specifically about the broader population.
In that context, I think your assessment that 'old GUIs' were more user-friendly is very rose-tinted. Back in the early 90s when those GUIs were everywhere, personal computers came with documentation, usually still on paper, because the devices weren't even user friendly enough that a typical purchaser could power on the computer and view documentation without help. And even then, these purchasers were a tiny subset of the population, typically with high educational achievement.
This was a time when public opinion hadn't even yet tilted in the direction of considering computer literacy to be a skill useful outside of an office building. Computer skills were definitely (and even to some degree still is) something people would list on a resume.
Consider the introduction of iOS. Windows Mobile had more features, more applications, was available on cheaper phones, and was entrenched in the business market at the time. It even followed traditional Windows design patterns, and applications often had a menu bar, as to your preference. They had plenty of documentation, and a link for 'Help' was always just a click away inside the Start Menu.
So, why was iOS so successful? It wasn't because power-users like you and I switched over. Many power-users mocked the device. It wasn't successful for including user documentation, it didn't and still doesn't. iOS was successful because it could be used by people who were unable or unwilling to read and follow documentation before using such a device.
Computer literacy is certainly a good academic initiative, but it won't help you make successful software for the mass market. The vast majority of casual computer users won't pursue educational endeavors to use your application. Most will opt for an alternative that doesn't require it, or they won't use it at all.
You should always consider the intended audience for your application. In our information bubble we sometimes lose an accurate perspective of the skills of the general public. This is of little consequence for many applications, but if your application is truly intended for the general public, like a government website, it's something that might need to be highly prioritized.
In that context, I think your assessment that 'old GUIs' were more user-friendly is very rose-tinted. Back in the early 90s when those GUIs were everywhere, personal computers came with documentation, usually still on paper, because the devices weren't even user friendly enough that a typical purchaser could power on the computer and view documentation without help. And even then, these purchasers were a tiny subset of the population, typically with high educational achievement.
This was a time when public opinion hadn't even yet tilted in the direction of considering computer literacy to be a skill useful outside of an office building. Computer skills were definitely (and even to some degree still is) something people would list on a resume.
Consider the introduction of iOS. Windows Mobile had more features, more applications, was available on cheaper phones, and was entrenched in the business market at the time. It even followed traditional Windows design patterns, and applications often had a menu bar, as to your preference. They had plenty of documentation, and a link for 'Help' was always just a click away inside the Start Menu.
So, why was iOS so successful? It wasn't because power-users like you and I switched over. Many power-users mocked the device. It wasn't successful for including user documentation, it didn't and still doesn't. iOS was successful because it could be used by people who were unable or unwilling to read and follow documentation before using such a device.
Computer literacy is certainly a good academic initiative, but it won't help you make successful software for the mass market. The vast majority of casual computer users won't pursue educational endeavors to use your application. Most will opt for an alternative that doesn't require it, or they won't use it at all.
You should always consider the intended audience for your application. In our information bubble we sometimes lose an accurate perspective of the skills of the general public. This is of little consequence for many applications, but if your application is truly intended for the general public, like a government website, it's something that might need to be highly prioritized.