[SWIFT] About Milkcocoa SDK

Hello @syuhei.

The Milkcocoa logo is now capitalized. Officially, it is Milkcocoa in capital letters like this, so thank you. Today, I will write about the SDK (Software Development kit) of Milkcocoa. We are developing the SDK at high speed because we want you to use Milkcocoa in various places. It may not be possible to reach some points, but please contact us in that case. If you can get @rip on Twitter, it will react relatively fast.

SDK currently available

The Milkcocoa SDK currently being provided, which is also described on the site, is as follows.

--Browser

Node.JS
Java

Thanks to you, there are quite a lot of tutorials, samples, and user articles about these SDKs. @I_ka_rashi introduced the Java SDK in Milkcocoa Meetup vol 5. I think it will be written about it in tomorrow's minutes of Advent Calender. This time, we will introduce other SDKs. Actually, there are several SDKs whose source code is currently published on Github.

Among them, there is an introductory article about the SDK for ESP8266 in Milkcocoa Engineer Blog. Regarding the Python SDK, there is an article (Try Milkcocoa Python SDK) written by python milkcocoa ngi644. The Python SDK seems to work with Pepper too!

Many of these SDKs have not been implemented, especially in terms of functions, so we decided to provide them as OSS (Open Source Software) so that they can be used by everyone as soon as possible. We are also considering making it easier to implement the History API by publishing the HTTP specifications.

About license

Most of these SDKs are licensed under the MIT license. If you find something strange, feel free to fork, fix it, and submit a Pull Request or Issue. For reference, each SDK is developed using the MQTT library as shown below.

Swift SDK(https://github.com/emqtt/CocoaMQTT)
ESP8266 SDK(https://github.com/adafruit/Adafruit_MQTT_Library)
Python SDK(https://eclipse.org/paho/clients/python/)

Summary

I'm really looking forward to seeing how the service Milkcocoa grows in the community. I think that making the client SDK OSS is the first step. I look forward to working with you!