It vexes me that UI books written by current IT practitioners inevitably descend into API-call-fest—a code dump, as it were. This sort of presentation is ineffective. In fact, it is childish.
A typical #programmer in IT who designs and implements a non-trivial UI, webtop or desktop, is seasoned, experienced; he knows how to use an API. But he does not necessarily have a background in usability:
PSYCHOLOGY
• The #psychology of visual and tactile perceptions
• The psychology of human-computer interaction #HCI
• The design and administration of psychological experiments on interaction and usability
• The design of the interaction flow
LIBRARY SCIENCE
• The design of the underlying information architecture
• The design of information layout
VISUAL ARTS
• The effective use of colour
• The effective use of font
There are tonnes of other usability-related subjects that fall way outside of modern CS curricula. The #UI books should aspire to teach these cross-discipline subjects on #usability to #CS and #IT practitioners.
Sure, code samples and screenshots of some popular UI framework would be helpful. But the main thrust of these books must be usability, with the organisation aimed at tech-savvy engineers and programmers, not novices.