Creating a SDK from scratch

Our Javascript SDK is one of the latest projects to be released and open sourced by Bynder. The acronym SDK stands for Software Development Kit, which is a quite vague description, so this project in concrete resulted in a Javascript library, obtainable through <a href="https://www.npmjs.com/package/@bynder/bynder-js-sdk" rel="noopener ugc nofollow" target="_blank">NPM</a>, that provides a simple and easy way of communicating with <a href="http://docs.bynder.apiary.io/" rel="noopener ugc nofollow" target="_blank">Bynder’s API</a>. <h2>Introduction</h2> Itall started at <a href="http://garagebeer.co/" rel="noopener ugc nofollow" target="_blank">Garage Beer</a>, one of the many craft beer places we coincidently have less than 10 minutes walking from our office in <a href="https://www.bynder.com/en/about-us/offices/barcelona/" rel="noopener ugc nofollow" target="_blank">Barcelona</a>, with a discussion that some of us belonging to integrations squad were having about the future of the team in terms of work and autonomy. At the time in Bynder, there were already several SDKs in an advanced state of development (such as the <a href="https://github.com/Bynder/bynder-c-sharp-sdk" rel="noopener ugc nofollow" target="_blank">C#</a> and <a href="https://github.com/Bynder/bynder-java-sdk" rel="noopener ugc nofollow" target="_blank">Java</a> ones) and we talked about how relevant would it be to have a JavaScript SDK to deal with the requests we were already having and to complement our offer in terms of integrations. And that’s how it all began. <a href="https://medium.com/bynder-tech/creating-a-sdk-from-scratch-2809ded9fa8a">Learn More</a>