Separation of Concerns

The wrong abstraction leaves you with a component shared in name only, with a riot of flags charting different paths. Here, we look at how to spot this cohabiting trap, and how to escape by letting each caller take back what is theirs.

Every iOS dev hears that whisper sooner or later: "These fields look the same…you should build a form-engine." Those who follow that whisper almost always end up with an over-abstracted mess. Here, we look at building a simple validation flow that keeps us on the right path.

Gaining insights into how our users use our apps is essential to fully serve their needs. However, gaining those insights can be messy. Here, we look at integrating analytics into our apps without it getting in the way.

Parsing an API response into an app type is fundamental to any networked app. Here, we look at how to build a consistent response parsing approach to make that task easier than ever before.

Following Single-Responsibility Principle, gives focus to your code and in turn your project. Here, we look at how to use that focus to find hidden modules, extract and keep them whole for the long-term.

View controller accumulate stuff. If you are not careful you can turn in a view controller into a hoarder's den. Here, we look at how to extract functionality from a view controller and rehome it using Single-Responsibility Principle.

Dependency injection is one of the superpowers that developers can utilise to produce code that is more predictable and easier to test. Here, we look at dependency injection - what it is and how we can utilise it.

Making a network call and consuming the response is common to most apps. But how do we do it well? Here, we look at building a networking layer to consume a SOAP response.