Let's get started development of API client library
summary
Argues that providing SDKs drives adoption and saves developers from raw HTTP, backed by concrete community SDKs: NIF Cloud Mobile Backend server-side libraries (Java, Ruby, PHP, C#) published on GitHub and distributed to NuGet, and Customer Mail Cloud SDKs (Python, Ruby, Node.js, Google Apps Script) enabling email sending from cloud functions and Google Sheets. Notes community SDKs are faster and idiomatic but often low-quality, require ongoing maintenance, and sometimes need full rewrites when APIs or coding standards change.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:27Developer Relations
- 5:48Developer to Evangelist
- 6:54API Vendor Level
- 8:35SDK is Important
- 9:23Development Environment
- 10:10Community Library
- 11:06Nifcloud mobile backend
- 12:45NCMBClient for NuGet
- 13:41Customers Mail Cloud
- 15:24Pros
- 20:24Cons
- 20:34Let's develop SDKs!
related talks
27mSDK or Not
26mSupporting SDKs in seven different languages while maintaining sanity
18mSimplifying Consuming APIs for SDK Haters
43mClient Library Design Stories
38mA Developer's-Eye View of API Client Libraries
32mBuilding Apps with an API-based Backend
27mSDKs & Code Samples, The Cornerstone of API Developer Experience
26mAsk your Developer: the rise of the API company