Design of Everyday Swift
summary
Argues that Don Norman’s design principles map directly onto Swift code and developer UX, demonstrating a tiny one-view controller (≈20 lines) built with programmatic auto layout using NSLayoutAnchor that initially fails until setting translatesAutoresizingMaskIntoConstraints = false, after which it runs. Recommends concrete practices: use access modifiers, tests, clear names and project grouping as signifiers and mappings, rely on compiler errors and the Swift type system as constraints and immediate feedback.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:41Summary
- 3:42Who Are Our Users as Developers
- 8:24Seven Stages of Action
- 9:30Principles of Design
- 10:50Discoverability
- 13:27Comments and Documentation
- 14:02Feedback
- 16:28Human Feedback
- 16:58The Conceptual Model
- 19:18Affordances
- 20:42Signifiers
- 22:52Mappings
- 23:56Constraints
- 24:54Recap
related talks
20mHow Not to Write Swift
39mThe Art of Designing Code
31mMaking the Most Out of Swift
21mOptimizing Swift code for separation of concerns and simplicity
18mBuckets of Code
11mFinding the Implicit Design
55mFrom Design to Swift: Best Practices in App Development - ROUNDTABLE
26mAdapting to change: design patterns in Swift