Experimental Swift

So we’re talking about a toy for big boys and girls here – Raspberry Pi. Yes, you heard me: iOS + Swift Server + Raspberry Pi. It seems trivial when reading Piotr’s post but the first thing I thought about was how to set up an environment?! 😱 Fortunately, Piotr has got us covered with a step by step guide through.

Back Buttons and Coordinators

A little bit late but we just couldn’t miss this one! As always, Khanlou did a great job with another article about the Coordinators pattern. It may seem like an edge case, nevertheless, it can happen to anyone and it consumes way too much time.

Protocols and MVVM in Swift to avoid repetition

Do you want to avoid repetitive code or move some of your code from a View Controller? You can do so in just a few simple steps. Grab your weapon to fight against MassiveVC – MVVM and protocols to the rescue!

Using lazy properties in Swift

John keeps a good pace on his new website. This week, he takes a look at a few ways to define lazy properties in Swift, and how different techniques are useful in different situations.


This is for all the dinosaurs: improving Objective-C codebases, in times of the Swift hype, is as challenging as mastering protocols.


Basic Patterns of Mobile Navigation

Hamburger Menu, Tab Bar, Priority+ Pattern, Floating Action Button, Full-Screen Navigation, or Gesture-Based Navigation. Which navigation pattern to use and when? The strengths and weaknesses of each are described in this article.


The Two Sides of Writing Testable Code by Brandon Williams

It may seem like just another reminder of the advantages of writing testable code – nothing further from the truth. With just the right amount of theory, Brandon will show you the complexity that may be hiding in your codebase. The refactoring of a seemingly simple method, which can be found in a whole lot of OOP projects, shows us how to rid the code of all hidden dependencies and how to make it stateless and functional-oriented.

A Neatly Typed Message: Improving Code Readability by Krzysztof Siejkowski

Finally, someone has pointed out that stacking abstraction becomes a readability cost after a rather brief period of time. And readability cost means maintenance pain for most of large codebases. A great lesson about how to estimate if that sweet enum or typealias is just a one-time use cost generator.

As always…

If you have something interesting to add about our technology, don’t hesitate to send it to us via e-mail.