Building Platforms for Developers
summary
Uber documents how it turns a complex microservice stack into usable developer products: launches ride request API (after deep links), adds trip experiences webhooks to replace polling, and exposes program-built endpoints like deliveries and drivers. Scale numbers: 1.5M partner drivers, ~5M trips/day, 2B trips total, 3,400+ microservices. Deliverables include SDKs, one‑page tutorials, useful error messages and a developer sandbox that simulates real trips; result is broad third‑party integration (Citymapper, Google Maps, Alexa, Auto) and far fewer support tickets once docs and tooling land.
AI-written summary · about
chapters (8)
- 0:00Introduction to Uber platform
- 2:04Hackathons and API origins
- 7:01Building platform ecosystems
- 14:49Developer product structure
- 21:27Developer advocacy and feedback
- 27:04Documentation and error handling
- 34:07Lessons learned scaling platform
- 37:24Q&A on API design
related talks
48mMobile Developer Productivity at Scale
02mMeet our speakers: – Matas Strukčinskas
24mHow to make your API Platform easy for Developers to Adopt
39mMobile Developer Productivity Panel
26m5 billion API hits that have accelerated customer outcomes
26mUnlocking Revenue: Transform Internal APIs for External Use
56mWhat are the means to accelerate the API strategy
37mJava Diary of an Uber Driver