It was in January when I blogged about Redux on Android and, around the same time, I've started implementing a solution in Kotlin.
My purpose was not to do the n+1 implementation of Redux, but more to provide a solution that can be used in conjunction with some of Kotlin's new language features like coroutines, to handle asynchronicity for instance.

Some time ago a colleague offered a cake to anyone who could assist in integrating Google's calendar and resource API. So, I do like cake and thought that I should give it a try. I started playing with the mentioned APIs and as usual, Java 8 has been chosen as a starter, which quickly led to some first results, but it would make sense to put some effort into creating a mobile application. Unfortunately, I didn't know much about Android yet, except that it's based on Java 6, resembles Swing programming and defines some custom lifecycle strategies.

Creating an armhf image on a different hardware platform requires five to ten times more patience than creating the same image on a native platform. A few months ago I've started with Travis CI to build the official docker images for armhf and very few images always exceeded to maximum build time of 50 minutes, due to some costly compilation steps. 

Some time ago, I investigated how to switch from a manual docker image generation to an automated process for armhf based dockers using public CI servers. Building on a dedicated target hardware is still preferable, but most Open Source CI systems run on an x86/amd64 host at the moment.