2 hours ago, svelasquez wrote
Patience level varies considerably and many will just write their frustrations off as poor design.
If your features aren't discoverable, then your UI is badly designed. Your UI is about showing off your functionality. If your user wants to do something it is the job of your UI to get them to a button that'll do the action they want as quickly as possible. If you have to search the Internet to find a feature in your app, then your apps UI has failed. In this regard, at least, Windows8's UI has got in the way of Dr Herbie doing what he wants compared with Windows7, and that is a direct failure of the Windows8 shell UI team.
I agree with what I think Dr Herbie is saying in that there needs to be a tutorial or temporary how-to functionality to help users that will not even bother trying to find an answer to their question.
I disagree. There is a significant percentage of the population who don't engage with tutorials because they "just want to get started". They'll right click and press escape and space bar and click on as many red-crosses as is necessary to skip your tutorial and then complain later when they can't do something that was explained in the tutorial. It's easy to blame them and say that's their fault, but on the other hand, if your UI isn't obvious without a tutorial or a manual, maybe your UI isn't very good.
If I were on the shell UI team, I'd take a leaf out of the computer-game industry's book and make every loading screen in Windows8 give little popup "hints" for how to use Windows. These would give you clues as to hidden features like shortcut-keys, upgrades, enhancements and so on during Windows boot and during Metro app loading and so on without requiring interaction or slowing down someone's ability to "just use" the OS. Nobody wants to sit down and read a manual, but if you're forcing the user to wait (during boot etc) you might as well make use of the time they're staring at the screen and doing nothing.
Add your 2¢