Type-driven User Interface Design
summary
Proposes using static types as the primary design artifact: build a small formal model for an import dialog using product and sum types, enforce the rule make illegal states unrepresentable, then mechanically map types to UI widgets. Example: a File -> file picker, a Json|Yaml sum -> radio buttons, loading/upload sums -> spinner, error view, ready button and final link with entity ID. Claims the model is precise, simple, separates essential from accidental complexity, and yields a usable UI without guesswork.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:47Classic UI limits
- 5:21Functional design approach
- 9:32First model with types
- 12:02Illegal states unrepresentable
- 14:53Type-driven UI process
- 23:43Conclusion and key takeaways
related talks
09mModels instead of high‑fidelity UI designs
25mLeveraging (algebraic data) types to make your UI rock solid
50mLet's Design UI the Right Way
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
52mNo Nonsense UI Design
14mDesigning UIs without a UI designer
26mMerging Design and Developement
28mIt’s Easy to Create a Good looking Product, but What About a Useful One?