Success of your framework depends on your API

on YouTube ↗29m

" summary

Companies at 1mg report search APIs that ask for 10 items but return 4–20, backend responses that silently wrap errors as 200, and a Safari scrolling bug tracked since 2016; fix patterns are Absolutely Predictable Interfaces that are hard to misuse and avoid returning error-via-200. A framework called Catalyst exists after four years of work, open-sourced, with a single fetch API that works both client and server, supports publishing native Android/iOS webview bridges, and is demonstrated as functional.

AI-written summary · about

" chapters (12)

1. 0:00Intro
2. 0:30API
3. 1:30Bad API
4. 6:38N stars
5. 11:02Scale of Operations
6. 12:40Scrolling
7. 13:07Overflow
8. 14:43Position sticky
9. 16:13What do we do
10. 16:27Recap
11. 19:28Demo
12. 24:14Catalyst

" related talks

• 35mBuilding Your API for LongevityMike Stowe · RubyConf 2014
• 47mAPI Tips from the FrontlineAnna Filina · International PHP Conference Spring 2017
• 26mDesigning Accessible APIsDave DeLong · try! Swift NYC 2019
• 24mWhy Your API Adoption is Failing & How to Fix ItNolan Di Mare Sullivan · apidays London 2023
• 47mKilling accessibility with five wordsAlmero Steyn · Inclusive Design 24 (#id24) 2018
• 31mFramework Design - Lessons Learned from Repeated MistakesRouben Meschian · JavaScript Conference Armenia 2018
• 18mBuild a terrible API for people you hateJim Bennett · apidays New York 2024
• 20mThe Last Line of Code, Your API is Never FinishedMichael Wawra · Platform Summit 2014