8. Other signals you may not need SDKs
● You are still proving the value of your API
● You only plan to service a handful of developers
● You don’t have many endpoints and simple data structures.
● You don’t have strong competitors
● Your offering is so compelling developers are willing to put in extra effort.
● Target users don’t use SDKs (10x engineers or low code/no code)
15. Stripe’s server-side helper libraries (also
known as server-side SDKs) reduce the
amount of work required to use Stripe’s
REST APIs, starting with reducing the
boilerplate code you have to write.
❝
❞
27. Over 50% of support inquires were
authentication related
Our forums filled with developers sharing
code snippets and trying to help each
other.
More API wrappers built by community
and shared on GitHub - but they weren’t
well maintained.
Headaches all around
28.
29.
30. Signals we needed SDKs
● Time to first Hello World is subpar
● High support burden
● Developers asking for examples in different languages
● Community building their own libraries
● Key accounts are asking for SDKs
● Your competition have SDKs and offer a superior DX
35. SDKs that are easy to use
● Implement a REST-agnostic design
● Design Consistent SDKs
SDKs that come with docs
● Create SDK specific documentation
● Provide Sample Code
36. SDKs that match the API
● Ensure API Coverage
● Provide End-to-End Typing
SDKs that work
● Create a Test Suite
● Share Test Coverage Reports
37. SDKs that are robust
● Transient Error Policy
● API Error Policy
SDKs that receive updates
● Timely API Updates
● Security & Maintenance Updates
38. SDKs that have support
● Handle support tickets
● Engage with the community
40. ● Architect or Program Lead
● Developers to create the SDKs in each language
● Content writers to create documentation
● Support staff who handle support tickets
● Developer(s) who owns SDK updates when API changes,
language changes, bug fixes, and dependency updates
● Developer Relations team or person to engage with the
community on SDK and API roadmap and their experience
41. Ways to Build SDKs
● Homegrown or Handwritten
● Open source code generators
● Commercial code generators
42. Recap
● SDKs are more than code libraries
● SDKs reduce boilerplate code, complexity, help with change
management and developer achieve “flow”
● Every API doesn’t need SDKs
● Signals to watch for that you might need SDKs
● Establish what a good SDK means for your community
● Use your criteria to evaluate ways to build SDKs.