UX Is Frontend Only! Why Do I, Super Ninja Backend Developer, Need to Care About It?
summary
Good UX changes API shape, database schema and query plans: teams report 25 database requests per HTTP request and endpoints that return 100 MB of JSON for a simple signup, both fixed by aligning UI flows with backend models. Practical prescriptions include using correct HTTP verbs and status codes, documenting libraries, running Figma prototypes against real data, and validate at least six times with meaningful, consistent error responses so integrations and performance actually improve.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:58Why UX matters for backend
- 3:25User experience fundamentals
- 6:59Developer experience is UX
- 8:46API design best practices
- 10:34Constraints and input validation
- 12:40Feedback and error handling
- 15:33Designing for failure
- 17:00Role of designers in development
- 18:44Design process overview
- 20:31Collaboration and iteration
- 21:34Solving the right problem
related talks
54mAgile UX - How to Combine Agility with Usability
22mUX crash course - What is good UX about?
37mThe UI is THE APPLICATION
38mUX Is a Team Discipline
15mEnhancing Developer Productivity with UX
34mUnderstanding UX (and UI) – a practitioner's perspective
24mYou're Doing UX Unconsciously, Now Let's Make it Conscious and Intentional
49mUX and an Agile Development Process