SDK as the User Interface
summary
Claims that SDKs act as the product UI and that automation removes repetitive work by generating and maintaining SDKs, docs and runnable examples from a machine‑readable API description. Uses continuous code generation with Jenkins and Travis to build test and deploy SDKs; cites ~50M developers and a survey claiming ~83% of SDK effort goes to maintenance. Demo auto‑generates a portal, multi‑language SDKs and runnable interactive code samples, publishes to GitHub and npm and completes end‑to‑end in about six minutes.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:48How Many Developers Are There in the World
- 7:09Difference between Api Wrappers and Sdks
- 7:37Code Samples
- 8:25What Kind of Code Samples Are Important
- 13:38Continuous Code Generation
- 17:52Conclusion
- 20:26Calculator Api
- 21:10Generate Api Portal
- 22:21Add a New Github Repo
related talks
27mSDK or Not
27mSDKs & Code Samples, The Cornerstone of API Developer Experience
30mDeploying and building SDKs as a service Developer
14mAgent-Driven Software Development
09mDeveloping and supporting 12 SDKs with a team of three
22mSDKs, Relations, Love & Thunder
34mWhy SDK Docs Matter — And What I’m Doing About It!
53mHow not to fuckup with building SDK and make clients happy