UX from a developers perspective: the influence we can have
summary
Developers make dozens of tiny UX decisions every day that accumulate into a product’s experience: a concrete example is the forgot password flow where choosing a 10‑minute expiry and a generic error forces support calls, while changing to a 4‑day expiry plus a direct reset screen and actionable message is “two lines of code” and cuts friction. The practical toolkit: invite us to the UX club, ask developers for multiple options, and teach core UX principles so engineers choose better defaults.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 1:50Developers make UX decisions
- 3:58Example of poor UX decisions
- 7:16Impact of small UX changes
- 8:39Intervene or empower developers
- 10:28Invite developers to UX community
- 11:31Ask developers for options
- 12:58Help developers learn UX principles
- 13:39Call to action for UX teams
- 14:21Developer responsibility in UX
- 15:45Closing remarks
related talks
42mUX for developers... Say what?!
22mUX crash course - What is good UX about?
12mStart Using UX as a Weapon
36m"UX for Developers, Seriously!"
37mThe UI is THE APPLICATION
28mDesigning for Success: UX Principles for Internal Developer Platforms
34mUnderstanding UX (and UI) – a practitioner's perspective
36mTop things we need to learn about UX