Build for ALL of Your Users

on YouTube ↗17m

" summary

A case study of a chat API shows websockets for realtime plus REST endpoints that mirror the database, forcing clients to fetch profile photos via a photo ID then an S3 URL that may change, which in the worst case requires 765 requests when a 256‑member group adds someone and balloons costs and latency. Recommendations: architect with intent (batch endpoints or embed URLs), dogfood and build sample apps, provide open API spec to SDK generation (liblab style), run user interviews and measure typical/worst latencies.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:31APIs lack user-centric design
3. 3:18Hypothetical API scenario
4. 4:24Real-time chat API structure
5. 6:29Profile photos expose API flaws
6. 8:15Engineering challenges from API limits
7. 10:47Building APIs for all users
8. 12:56Improving API design steps
9. 14:43Dogfooding and samples
10. 15:43SDKs and tooling
11. 16:47Closing remarks

" related talks

• 27mBuilding Great Web APIsMike Amundsen · apidays New York 2020
• 39mUser (developer) experience of your web APIAvinasha Shastry · Meta Refresh 2013
• 27mUser focused API DesignRenato Oliveira · PyCon 2018
• 32mBuilding Apps with an API-based BackendTim Anglade · Nordic APIs Stockholm 2013
• 35mBuilding Your API for LongevityMike Stowe · RubyConf 2014
• 28mWhy social engagement APIs are essential to your KPIsSid Suri · apidays Paris 2021
• 29mUser experience is everythingDag-Inge Aas · JSConf Iceland 2016
• 37mBuilding Apps that ScaleKilo Loco · droidcon San Francisco 2022