Merging Design and Developement
summary
Argues that treating UI as a pure function of state (from Pure UI) is incomplete and designers must model distributed systems and consistency like engineers — demonstrates with optimistic writes (team-name edit), retry and duplicate risks, and how WhatsApp checkmarks expose local vs remote replication. Recommends persisting local writes to disk not just memory, treating local UI as a small database, and aligning UI expectations with backend guarantees (ACID/partial ordering). Uses Consistent UI as the goal: surface in-progress vs committed state so users aren’t misled.
AI-written summary · about
chapters (7)
- 0:00The UI consistency challenge
- 2:13Defining distributed systems
- 5:53Beyond lorem ipsum data
- 9:17Local versus remote state
- 12:25Learning from WhatsApp
- 17:50Databases and consistency
- 23:28Key takeaways for designers
related talks
14mDesigning UIs without a UI designer
36mConsistency is Key - Working with a Design System
15mHoly War between Designers & Developers
28mDynamic UI at the Edge
49mBuilding Event Driven User Interfaces
54mHow to build the modern, optimistic and reactive user interface, we all want.
41mThe UI/UX Benefits and Trade-Offs of Local-First Apps
36mUX designers /developers collaboration anti patterns