>"Instead, telling your customer the exact button to press and why they should press it is a much more helpful prospect." //
I think I also disagree on the false-feedback he suggests is good. If you give immediate UI change on a like showing that it has been registered and then you can't register it you find that user experience can break trust - next time I go to that page/post/comment I see my "like" is missing yet the UI showed it had been registered. Surely this is a place for an intermediate state?
Similarly with the skeleton screens, it can lead to a situation like the one he has with his videos being missing. The page changes but it's not got content, but there's no loading indicator as there is elsewhere on the site/in the app - so is it loading, did it break? We're left guessing about what is happening.
Petty complaints follow:
>"Awkward UI is a missing a loading indicator." //
Oops. There are always errata!
Surprised to see the segment on loading indicators avoid using the word "feedback".
>"Even if you're creating weather apps (cue Dribbble joke), one state won't cut it." //
Will the targeted readership understand this reference, I don't. I even went to Dribbble.com for illumination but none came.
I see a lot of missing [obj] which appear to be mostly/all "" being used as a section marker. It appears not to exist in the chosen font on my system though? [latest FF on WinXP]