SDK news II.[email protected]om Czech RepublicMember, Administrator, Kentico Staff admin

Hello again!

Together with today's sample app news, we've got even more great news to share regarding our SDKs. If you haven't been in touch lately, then this is a wrap-up post that sums it all for you.

New SDKs

Some of you probably noticed that since the last SDK news, we brought quite a few new kids to the block:

Content Management .NET SDK

Yes, the much acclaimed Content Management API has its .NET SDK out of box. Importing, exporting, and other management of all your content via API is just a matter of getting an access key and calling an endpoint. If you're a .NET developer, than it is just a matter of adding a NuGet package.

Besides the .NET SDK, we've created an awesome import tool that streamlines the most frequent tasks of importing content. It was created with Node.js and you can use it either online or whip up your own instance. The tool has both a user interface and its own easy-to-use API. Be sure to check it out!

Delivery PHP SDK

The dreams of all of you, PHP developers, came true. The SDK is a feature-complete complement to all our other SDKs. You can start using it via a Packagist package.

Delivery Node.js SDK

This new SDK originated from the existing JS/TS SDK and it uses the JS/TS SDK in the background. That means you get all the benefits of the existing SDK in your server-side apps.

Delivery JavaRx/AndroidRx SDK

The reactive approach is highly popular these days in the Android and other native app development. It takes the burden of handling events, updating the UI, dealing with concurrency and resource cleanup off the developers' shoulders. Now we have an SDK where Rx is a first-class citizen. You can use it via any of its binary packages now.

New Features in Existing SDKs

Delivery .NET SDK

We now support secured access to the Delivery API with a security key. This way, you can create authenticated sections of your sites while still leveraging the worldwide content caching via CDN at the same time.

We also added automatic type filtering to the SDK. When you call deliveryClient.GetItemsAsync<Article>, you no longer have to add that new EqualsFilter("system.type", "article") to your call.

Delivery Java SDK

As in our .NET SDK, here, you also get the benefits of the secured Delivery access and the automatic type filtering. On top of that, the SDK now has a built-in retry logic against transient network faults, it parses the inline modular content items and supports the Joda time format.

Delivery JS/TS SDK

Apart from serving as a background technology for the above Node.js SDK, it now has a property decorator.

Personalization .NET SDK

The Personalization .NET SDK now allows you to track your custom-tailored activities.

Wrap Up

As you can see, there's been lots of happening in the past months for our SDKs. The vast majority of the features was directly inspired or even created by you, developers. So don't hesitate telling us what would be the next great thing in our SDKs. If you want to jump in with your own feature or design but don't know where to start, tell us and we'll guide you all the way through. If you'd like to just pick an existing issue to shape SDKs a bit more, a good starter might be, for example, adding the retry logic to the Delivery .NET SDK.

Lastly, let me say a big THANK YOU to all you community members for your interest and efforts!


Sign In or Register to comment.