User (developer) experience of your web API
summary
Design work for SupportBee’s API targets real friction points: a Backbone single‑page app backed by a JSON‑first API with XML optional, webhooks and web sockets for pushes, SDK wrappers in Ruby/Python/etc., and Swagger‑generated docs plus an “apidocs” open source generator. A hosted app platform lets third‑party apps deploy in 49 minutes to deploy and simple integrations (Campfire) run in 30 lines of code. Test accounts, stable versioning and schema discovery cut integration time; observed integration uptake sits around 10–15% of customers.
AI-written summary · about
chapters (8)
- 0:00Introduction developer experience
- 2:14Why API design matters
- 7:13Hypermedia and REST myths
- 15:11Building platform APIs
- 23:11Local development challenges
- 29:33Documentation automation
- 34:51Hypermedia for discovery
- 37:27Encouraging API adoption
related talks
27mUser focused API Design
27mGetting developers hooked on your API
27mWhy your API portal is so bad and what you can do about it
37mBuilding Developer-Centric APIs in a Multi-Product SaaS Org
24mHow to make your API Platform easy for Developers to Adopt
27mBuilding Great Web APIs
26mAsk your Developer: the rise of the API company
28mFrom API Products to Platform Thinking: A Strategy Guide