Attention!Notre centre de support est actuellement en train de se refaire une beauté. Pour accéder à l’ensemble de nos articles, merci de visiter notre site en Anglais ici.
To explain Software Development Kits (SDKs) come journey with me back to the early 1900s, when large retail companies sold kit houses by mail order. You'd know you wanted a house, and you had an idea for what it should look like, but who had the time to go out and figure out exactly what materials they needed or what configuration they should go in? That's where the kit houses came in: select one out of a catalogue, send off your money order, and then a disassembled house would show up some time later. You could assemble the house to do what you want, without having to know how to figure out how many joists you need or what kind of tile would fit best on the roof.
An SDK is much the same sort of thing, but for APIs. (See our other article on those.) An SDK is a piece of software in your chosen programming language that you can install in your application to make use of an API, without having to know every intimate detail about the API itself. Like a kit house it takes away some of the decision making you'll need to do, but it also makes it so that you can go from an empty application to a functional piece of property (or whatever) in much less time. You still need to correctly use the SDK -- but you don't need to worry about manually implementing every single part of the API.
You can use our SDKs to get started building your dream house, er, application just that much more quickly. We can't wait to see what you build!