Articles

If you want to become a complete senior iOS developer, you need to learn how to develop good apps regardless if you're using UIKit or SwiftUI. That's because frameworks are implementation details (including UI frameworks!).

If you want to become a complete Senior iOS Developer, you need to learn how to make solid architectural decisions instead of blindly following templates. This includes VIPER templates that, when followed blindly, can lead to messy, buggy, and over complicated codebases.

If you want to become a complete senior iOS developer, you need to manage memory usage correctly (NOT only in interviews but also in real-world projects!). So watch this practical mentoring session now!

To become a complete Senior iOS developer, you need to learn how to refactor existing code with confidence... But what does that mean?!

It's easy to get away with inefficient code when dealing with small iOS apps manipulating small amounts of data. But to become a complete Senior iOS Developer, you need to also be able to handle LARGE data sets in your iOS apps. And that's where optimizations become essential.

To become a complete Senior iOS Developer, you also need to know how to work effectively with legacy codebases... And this is what this mentoring session is all about.

If you want to become a complete Senior iOS Developer... You need to learn how to understand the clean architecture diagram and how iOS, UIKit, SwiftUI, CoreData, URLSession, Entities, etc., fit in the layers. And that's exactly what you'll learn in this live mentoring session, including guidelines for modularity, automated testing, access control, Dependency Injection, and optimizing the CI pipeline.

Learn good questions to ask your interviewer in iOS interviews, what to say when you don't know an answer or disagree with the interviewer, and many more to progress in your iOS dev career and become a complete senior developer.

Learn why and how to handle concurrency in iOS apps. Also, how to decide between delegates or closure callbacks.

"If you decouple Use Cases from Core Data behind a repository abstraction, how can you `rollback` changes on errors to guarantee transaction consistency?" Watch this video now and learn how to maintain transaction consistency with Core Data or any other repository implementation.

Learn how to test reactive RxSwift or Combine code in practice and Model/ViewModel separation best practices to decouple business logic from presentation logic.

Learn a clean and simple way of chaining many network requests in Swift with the Combine framework, including requests that depend on the response of another.