Do you want a SDK with that API?

Подписаться 10 тыс.

Просмотров 4,5 тыс.

50% 1

Holger Reinhardt from Layer 7 Technologies talks about when to use and when to not use an SDK for an API. Does for most developers consuming a public API in reality mean to consume a SDK? What are the implications for API providers? Does the API program target just the API, the API and a SDK or a SDK only? Looking at the IoT space, the availability of a SDK covering a wide range of platforms appears to become a crucial market differentiator. New services like IFTTT and Temboo enable the use of APIs without any technical knowledge and make them accessible to new consumers and users segments. A wide range of different models for SDK support exists. This talk will look at the emerging patterns of providing a SDK in addition to an API.
The presentation was recorded at Nordic APIs Copenhagen, a part of the Nordic APIs tour 2014.

Наука

Опубликовано:

7 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 2

@lovelyjavid 2 года назад

This feels like it was filmed yesterday. It’s still very relevant.

@domaincontroller 3 года назад

01:24 SDK, roll back on six, seven years ago, CD 01:41 library and everything else is on the web 02:20 value chain of an API 03:11 API value design 04:02 developer experience 04:15 an API passed the hype cycle and people don't really care about anymore if there is an API or what does this API looks like ? 04:39 Google 04:54 Is SDK the new API ? 05:04 segment.io, API broker, google analytics, dashboard 06:12 this is literally a screenshot of the developer page ---------------------------------------------------------------------------- Experiment --------------------------------------------------------------------------- 06:34 that's an SDK, a javascript SDK right 06:45 experiment with the fitbit API 07:33 development page, step up in terms of complexity 08:10 I didn't see JavaScript 08:49 I wanted client-side but got server-side 09:18 MacBook, PHP, set it out, google , stackoverflow, 2/3 of my day on it, enable, apache, server 09:50 my mood, I wasn't quite well, small annoyances, spending a day trying to run 10:05 except It wasn't the code I wanted it, It wasn't onthe side I wanted, had to install a bunch of frameworks 10:26 that code certainly looks complex 10:44 business developper, iOT 11:12 TEMBOO, selling you SDK with pre-built integration, selling you pre-integrated API's in it, I was done with one and half hour ---------------------------------------------------------------------------- Experiment --------------------------------------------------------------------------- 11:41 look at that SDl and the code, PHP, their data presentation kind of leak into my APi, there was no abstraction 12:29 it had all hundred 150 API in it , that doesn't right to me 13:08 OAuth flow in that PHP client 13:23 second thing, all the framework installed, was trying to teach XML parsing 13:30 JSON, webshow, oauth.io, what segment.io is for analytics, oauth.io is for oauth