We have introduced two new SDKs for performing identifier recognition in Android and iOS native applications. With these new SDKs, developers can seamlessly embed a item identification code (such as a QR code, EAN13, UPC-A, or other industry standard barcode) recognition experience into their own native branded app.

There is now a full walkthrough for the Reactor available in the Documentation section. The walkthrough aims to provide a good conceptual introduction to the features, use-cases, and types of events this feature supports, as well as many example implementation patterns to get the most out of it. After reading and following along in your own account, you will have a number of fully-working example implementations that perform a range of tasks including:

As part of ongoing security enhancements, we are updating the Application User API to introduce an additional check when updating the password field.

As many of you probably heard a severe vulnerability has been discovered in WPA2. This is important as WPA2 is the most widespread WiFi security protocol and it is used by a vast majority of routers, mobile phones, computers and IoT devices to secure WiFi communication. The details of the exploit (named KRACK) are available here so, in this post we focus on what's the impact for EVRYTHNG's customers and IoT devices.

As you probably have read we are phasing out our support for non-TLS APIs and forcing TLS 1.1+ for all communication with the EVRYTHNG platform. This is part of our continuous improvements to ensure that we keep your Thngs secure!

On the 23rd February we announced that we would be transitioning to a new security certificate ahead of the expiry of the old one, and also to upgrade from the deprecated SHA1 scheme.

As part of our ongoing security improvements, we will be removing support for JSONP, in favor of the much more secure CORS technology.

As part of our continuous efforts to improve the security of our platform, we will be upgrading our TLS policies.

We will soon be making some changes to how actions and Thng/product property histories operate. Currently, all actions and property update histories are preserved indefinitely for all Thngs/products on all accounts. This will change to introduce some sensible limits on how long these items of data will be kept around for free trial accounts. Enterprise accounts will not be affected as they benefit from access to our advanced IoT analytics tools.

Pagination of EVRYTHNG resources is not as straightforward as we would like it to be. The chief reason for this is that the behavior of pagination varies in small unpredictable ways depending on the type of resource that you are paginating. For example, there are different HTTP headers or query parameters that are not always available. As a result, integrating code needs to be complex, and performance can vary.