Exceptional Handling: DX as a Priority for API Products
summary
Panelists argue that DX wins on measurable specifics: reduce friction around time to first successful API call by fixing authentication, use token-onboarding like Slack token flow to cut hello world time, publish schemas and interactive docs (Salesforce uses Postman public workspaces and open source collections, Pinecone uses Midfi), track publisher metrics and forks to prove adoption (Salesforce reports ~2.6k forks), surface common errors like Stripe did, and prepare for AI as primary API consumer with strict schemas and usage‑based billing.
AI-written summary · about
chapters (13)
- 0:00Why Developer Experience (DX) should be a priority
- 2:10Introduction to panel participants
- 5:01What is a priority in Developer Experience today?
- 7:17How have API priorities changed over time at Salesforce?
- 8:12Are companies doing enough for Developer Experience?
- 12:04How can DX help you stand out from the crowd?
- 13:39How is the prioritization of Developer Experience changing?
- 19:50Will you lose customers due to poor developer experience?
- 21:41Does revenue factor into developer experience?
- 26:17What does success look like in developer experience?
- 30:02Turning problems into opportunities to improve DX
- 33:38What does bad developer experience look like?
- 37:30Predictions for developer experience in APIs
related talks
26mIs DX the new CX?
28mDevelopers are People Too! Building a DX based API Strategy
53mLet's talk about DX, Baby!
22mThe UX of DX: user testing in the invisible world of APIs
27mFireside chat: DX challenges and innovations
15mEnhancing Developer Productivity with UX
25mDo you know who's reading your Docs?
22mAPI Sandbox: empowering Developer Experience (DX)