The KNoT SDK allows the developer to read values from the KNoT Thing and publish them to the KNoT Cloud. This operation permits the developer to set timeouts and a range in which the values should be updated by the cloud. This operation is severely impacted by limitations of the Android ecosystem since many of the solutions can be battery and networking intensive.

The KNoT SDK should, if permitted, allow developers to read values from the KNoT Thing. This means that the KNoT SDK should provide an easy way to, given the right conditions (timeouts or limits), publish read values from the device to a KNoT Cloud.

The necessities that an Android application might have for the KNoT sdk are not clear enough. In order to get a better insight into this, it seems like a good idea to develop a basic application that utilizes the KNoT sdk.

In order to send/receive data from the Cloud, a Thing has to be authenticated. This is not different in the Android Universe. So, it's necessary to implement, all the steps required for authentication.

It has come to my attention that the ability to effortlessly transform Android devices into a KNoT Thing is a very desirable feature. Taking this into consideration, the development of a KNoT SDK targetted at the Android platform seems like a reasonable solution.

When creating the AMQP queue in the android app there are two viable options: create each queue with a hardcoded name or create a queue with a randomly generated name and enabling the auto-delete option for each queue. The first option creates a dependency on the hardcoded string, so if it's id is to be changed, the SDK would have to be updated. Since the auto-generated name does not imply said dependency, it seems like a more robust solution. Are there any reasons not to use the former option?

The Android SDK should allow the user to easily write values to the KNoT Thing. A write manager is needed to, after parsing a "write message", write the value to the correct sensor and do any kind of checks (e.g. value is in range) on the appointed value.

The KNoT Cloud uses WebSockets as its means of communication. In order to exchange messages with the Cloud, one should have a networking infrastructure, that takes cares of connection and error handling, to communicate with the server.

In order to receive/send messages to the KNoT Cloud, the Android SDK must parse the messages to the standard used by the KNoT platform.

The KNoT SDK should, if permitted, allow the developer to write values to the KNoT Thing. This means that the Android SDK should be able to receive a message from a KNoT Cloud, parse the message and actuate on it.