July 26, 2016
Ever since the creation of the IoT division at Monterail, we've been trying to solve one particular question. In terms of developing an IoT project from scratch, when should we use an existing IoT solution? At first, it seems that we could build an IoT project from scratch instead of using another platform. We have a talented team that can deliver beautiful and bulletproof applications. After deeper consideration, we agreed that this decision is more complicated that it seems and requires further investigation. So to answer this question, we conducted some research about IoT platforms that could speed up the development process.
The first one is Kii. Its website says that it can “speed up your IoT initiatives”. This is exactly what we want to do. It is a mobile backend as a service. What does that mean? It provides a middleware that stands between the firmware on a hardware device and the end-user application (website, phone app, etc.).
At first look, it seems that this is the perfect solution for most IoT projects. At the beginning of development, we should double-check how much the project can gain by using Kii.
|two different access levels||extensive configuration: user can set up wrong privileges by mistake|
|access levels can be customized||closed source of Kii|
|https and access tokens|
|cloud service, scalable to any size||none|
|huge number of features||custom scripts might not be efficient in big data|
|custom backend node.js scripts||old version of node.js|
|constrained list of allowed modules|
|code testing might be difficult|
|SDK in many languages||none|
|a lot of features||very time consuming|
|whole system is well-documented||search engine|