Recommended way to seamlessly gel UITabBarController with Coordinator pattern, where each tab has its own Coordinator.
First let’s see how it was done before iOS 13. Then we’ll take a look how scenes changed this setup. Spoiler: quite a bit.
Learn how to get the main benefit of my Coordinator implementation without actually using the library or the pattern.
I am having so much benefit from using this pattern in last few years, I can’t help myself. I have to try and persuade all of you to use it too.
How to implement true, tell-when-download-finishes Operation subclass
I went thoroughly through the great new book by objc.io authors. Given its topic, you can expect I have lots to say.
Replicating UITabBarController behavior using Coordinators flattens your UI hierarchy and thus considerably simplifies controller transitions
I have an opinion. Yes, I know that joke.
Expanded transcript from my talk at NSSpain 2017
“Avoid notification.object and userInfo”
Taking the first step towards clean and minimal app architecture in iOS app means freeing your view controllers from the burden of dealing with other controllers.