Let's put U in UX!
summary
Claim: API designers are UX designers and concrete rules for APIs map to UX decisions. Examples: a game backend on Google App Engine with remote DB, analytics and player management actually ships; UX checklist borrows Joshua Bloch’s API rules; real products cited — Stripe pricing, DigitalOcean/AWS calculators, Steam and Homebrew install flows, Uber flows — show what works and what breaks. Team context notes twelve UX designers and six design‑ops people supporting Dynatrace. easy to learn and hard to misuse
AI-written summary · about
chapters (13)
- 0:00Start
- 6:30Experience Is Not Ui
- 8:53Installation and Deployment
- 9:30Documentation Help and Support
- 14:25Good User Experience
- 16:53Carrie Server
- 17:44Get a Requirements with the Healthy Degree of Skepticism
- 20:59Agility Trump's Completeness
- 22:42Duke Nukem Forever
- 23:42First Amazon Website
- 25:05Make Your Product Easy To Use or Easy To Learn
- 27:59Amazon Buy Button
- 30:01Six Implementation Details Should Not Impact Your Api Should Not Impact Your User Experience
