Why iOS Developers Feel Stuck In Their Careers & What To Do

Why iOS Developers Feel Stuck In Their Careers & What To Do

This pattern indicates that iOS developers are looking to progress in their careers, which is fantastic! But they end up finding suboptimal solutions, such as deciding to become more “generalized” developers (constantly jumping to new technologies & frameworks).

Read More

Careful With “Singleton” Lookalikes (WAY TOO COMMON)

Careful With “Singleton” Lookalikes (WAY TOO COMMON)

Have you ever been told that Singleton is an anti-pattern? Well, Singletons can be ok, but if you are not careful, they aren’t just an anti-pattern. THEY CAN BE DANGEROUS!

Read More

Clean iOS Architecture pt.7: VIP (Clean Swift) – Design Pattern or Architecture?

Clean iOS Architecture pt.7: VIP (Clean Swift) – Design Pattern or Architecture?

Today we're going to analyze the VIP (Clean Swift) Architecture. And, as we did in previous videos with VIPER, MVC, MVVM, and MVP, we will decide if we can call VIP a Software Architecture or a Design Pattern.

Read More

Clean iOS Architecture pt.6: VIPER – Design Pattern or Architecture?

Clean iOS Architecture pt.6: VIPER – Design Pattern or Architecture?

Today we're going to analyze the VIPER iOS Architecture and decide if we can call it a Software Architecture or a Design Pattern like the MVC, MVVM and MVP design patterns we talked about in the previous video.

Read More

Clean iOS Architecture pt.5: MVC, MVVM, and MVP (UI Design Patterns)

Clean iOS Architecture pt.5: MVC, MVVM, and MVP (UI Design Patterns)

In this video, we're going to explore the main differences between the MVC, MVVM, and MVP design patterns.

Read More

Clean iOS Architecture pt.4: Clean Memory Management in Swift with WeakRef

Clean iOS Architecture pt.4: Clean Memory Management in Swift with WeakRef

We must be careful with `weak` properties as they can sometimes damage the design of our systems, especially when crossing module boundaries. In this video, we’d like to share with you a way to avoid retain cycles by using a `WeakRef` type, so there's no need to make your class properties `weak`.

Read More