Hardware is hard(er): designing for distributed UX in IoT
summary
Argues that IoT mixes the constraints of hardware and cloud software and gives concrete trade-offs: gas meter 30-minute reads vs electricity live data, LIFX vs Hue hub logic, and failure modes like a drone losing power or Canary removing cloud features. Shows hands-on tools and practices that worked: storyboards and service blueprints, Mural workshops, weekly demos, and mapping onstage/backstage flows. Useful if wanting concrete examples of what was built, why some designs fail, and how teams actually coordinate.
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:35Claires background
- 2:26What is IoT
- 3:10Hardware enabled services
- 4:49Hardware vs software
- 6:55IoT products are interconnected
- 9:09IoT complexity
- 9:51UX layers
- 12:19Technology
- 12:47Technical Architecture
- 14:47Connectivity patterns
- 16:51Proposition
- 17:17Understanding user value
- 18:40Thinking about risks
- 20:37Benefits outweigh risks
- 21:46Design angle
- 23:17Consistency
- 24:40Crossdevice interactions
- 28:49A story about team collaboration
- 30:17The importance of team collaboration
- 30:44How to facilitate collaboration
- 32:14Blueprint in service design
- 34:24What can you do
- 35:21How can you help
- 36:59Book competition
- 38:24Paper citation
- 44:59Remote working
- 47:44Whats good for engineers
related talks
28mThe awful design of everyday things
28mDesign Parallels: Architecture and UX
49mCo-creating with UX and Software
08mChris Hass - UXPA 2017
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
47mVideo
36mPositive Multi-Device Experience of the Future
46mThe UX of Work: Creating excellent experiences across hybrid workplaces