API users' feedback: why and how you get it
summary
Argues that continuous user feedback fixes blind spots, guides roadmap and pricing, and builds community; uses interviews, prototypes (Postman, Prism), usability tests with five+ devs, and card sorting — finding >90% misread “open” as free so APIs get renamed to self-service. Describes a failed beta testers community due to missing secure access, and a successful hackathon strategy (1,200 developers, supporting 50+ events) that surfaced 25+ portal/API issues via the Bank Hunter game.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:58Why care about feedback
- 3:10Find blind spots
- 3:36Build product roadmap
- 4:21Validate your business model
- 5:15Build community
- 5:52User interviews
- 7:22Prototyping
- 9:11Index cards
- 10:47Other options
- 12:28Halfway point
- 13:09Beta testing
- 15:30Feedback mechanisms
- 17:45Return of investment
- 21:32Conclusion
related talks
27mUser focused API Design
48mUser testing in production: how to run a public beta
47mUser testing in production: how to run a public beta
15mEnhancing Developer Productivity with UX
44mUser testing in production: how to run a public beta
24mLive API Teardown
30mDevelopers Are Pioneers Not Unicorns
49mBuilding Software Better: API Lifecycle Management for Developers