Best Practices in SDK Development
summary
32-minute practical checklist focused on SDK craft: use explicit access control and keep your API surface small (avoids the 40–50 exposed types problem), namespace via structs/enums, prefer typed request/response and settings structs over primitives, use enums for closed options and structs for customizable styles, write tests against the public API (watch out for Testable import pitfalls), publish DocC with manual topics, adopt semver after 1.0, and handle breaking changes via deprecations and typealias + @available renamed or message guidance.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 4:23What is an SDK
- 7:12API design best practices
- 13:17System design stability
- 18:59Testing public API
- 20:42Documentation strategies
- 24:13Versioning and deprecations
- 30:58Final takeaways and Q&A
related talks
28mLessons From Becoming an SDK Developer
26mDesigning Accessible APIs
22mBest Practices When Building Mobile SDKs
34mWhy SDK Docs Matter — And What I’m Doing About It!
32mHow to successfully shift from app development to SDK development
27mSDKs & Code Samples, The Cornerstone of API Developer Experience
53mHow not to fuckup with building SDK and make clients happy
22mMake your APIs Developer-friendly
