Adventures In API Design
summary
Compares shallow vs deep API boundaries using CascableCore (camera SDK) and Spotify metadata vs Crashlytics examples, arguing deep boundaries absorb chaos at cost of implementation work. Describes solving live‑view: move from push frames to a pull model by adding a completion handler, throttle and buffer to avoid memory spikes at ~40 fps. Describes hiding fragile camera state machines by serializing dual‑SD streaming and faking live view so the app never freezes. Concrete tradeoffs and working engineering fixes.
AI-written summary · about
chapters (7)
- 0:00Introduction to API design
- 3:15Choosing the API boundary
- 8:40Camera SDK adventures
- 15:52Push vs pull API design
- 16:34Handling fragile hardware
- 20:51Shallow vs deep API trade-offs
- 21:14Recap and key takeaways
related talks
21mThe power of unexpected APIs
27mAPI Design Through the Lens of Photography
49mBuilding Software Better: API Lifecycle Management for Developers
39mOnion-like iOS Architecture Solution
21mIntroducing The API Lifecycle
47mIntegrating modern native APIs with legacy code
20mThe Dark Side of Managing APIs as a Product
21mScaling API Design