Abstracting legacy and native dependencies from the Apple environment — Imagine you have an old part of your iOS app that requires new features and adaptations to certain flows for regulatory purposes. Additionally, you have a continuous integration system that blocks pull requests that do not contain enough tests, so every function and class must be unit tested in an…

Various ways to use the Observer class — If you work with object-oriented programming, certainly you are familiar with (or at least have already heard about) the Observer design pattern. This pattern consists of an Observable class that emits events with custom data attached to it. Other classes that subscribe to it may get a notification when a…

If you are applying to a software developer position, all the companies have their own technical interview templates and it’s impossible to have a preview about what will happen during the board. But something is certain: You will be given 10(or maybe a different quantity) minutes to ask anything you…

Declaring the data inside some computed properties — In the last series, I presented the first solution to organize your pipeline with three steps. At the same time, you will never be confused about which step should come first. Indeed it is a good coding practice. However, there is an issue regarding encapsulation. Since the methods for view…

An in-depth guide to best practices for your projects — Almost one hundred percent of iOS developers, except those conceived through SwiftUI API, started learning to build UI interfaces with storyboards. I still remember all the magic I experienced in 2017 when I took my first lesson about Swift by creating a simple Hello World app with a storyboard by…

Resuming our iOS VIPER series, it's time to talk about the most important design patterns that fit a VIPER scene. Since VIPER is a complex architecture, there are multiple ways to create and bind its layers, establish a relationship between different sides and make your code more legible. I might…

I think one of the most relevant questions regarding VIPER is about the separation of tasks between its layers. Its's clear enough, according to our previous article that View is only responsible of displaying our UI with proper content and build hierarchy; Router takes care of all context changes(popups, modals…

I know, I have already written several articles regarding VIPER and other clean architectures, including which one is the best that fits your project, but since my first article was written 3 years ago, with all the grown knowledge I got across these years, it's time to write in deep…

An in-depth guide into these fascinating areas — I have been developing iOS for the last five years and have worked for various companies — on different projects, architectures, teams, cultures, and approaches. As I have earned some experience in these huge environments, I decided to write this article for you, who is totally new to the corporative…