Intent in Software Design
summary
Argues that software must declare intent, showing concrete WordPress changes: screen options mix Ajax saves and a full-page apply button causing confusing mixed contexts, so 4.4 adds a poly-button and moves view modes into screen options; the image/link removed title attribute across releases because it hinders accessibility and tooltips; comment form reorders to put the comment first and de-emphasize URL; an ongoing fields API builds unified UI components and defaults so developers take the right path.
AI-written summary · about
chapters (15)
- 0:00Introduction to intent
- 1:23Intent in physical design
- 3:50APIs as user interfaces
- 6:19Developer and end-user UX
- 8:25Intent in field placement
- 9:10Naming and intent
- 12:21Backwards compatibility and intent
- 13:24Be intentional in design
- 14:07Q&A begins
- 14:30Optional fields in comments
- 15:55Title attribute accessibility
- 17:22Fields API overview
- 20:30Tooltips and inline help
- 23:04Designer-developer collaboration
- 25:15Closing remarks
