Advanced Coordinators in iOS

[@emilmicu9528]

Great insights, thanks for sharing. I'm using a similar approach, but instead of holding a reference to the coordinator I use a navigation delegate protocol for higher decoupling. This way the VC just informs the coordinator that the buy button was tapped instead of calling `buySubscription()`. So basically the VC knows only about itself and nothing else.

[@ragnacode56]

Every time I enjoy your tutorials! This one was awesome! Thank you!

[@shriyamgupta8217]

This is truly the best explanation out there for Coordinators in iOS! Thanks Paul!

[@alexl2512]

This is a great video worth watching multiple times.

[@byaruhaf]

Definitely one of the best videos on the Coordinator Pattern topic! Really enjoyed watching it! Great job, Paul & Soroush!

[@alexkiddens2199]

1. Child coordinators - kzbin.info/www/bejne/q5alqpVmgqeAh5Y 2. Navigating back - kzbin.info/www/bejne/q5alqpVmgqeAh5Y 3. Passing data between controllers - kzbin.info/www/bejne/q5alqpVmgqeAh5Y 4. Coordinated tab bars - kzbin.info/www/bejne/q5alqpVmgqeAh5Y 5. Using segues - kzbin.info/www/bejne/q5alqpVmgqeAh5Y 6. Protocols and closures - kzbin.info/www/bejne/q5alqpVmgqeAh5Y

[@VAIBHAVMISRA1987]

Thank you Paul. Every one of your video is immensely helpful and extremely practical. I definitely feel I'm a better engineer after watching your videos and trying them out in my projects.

[@t16incho]

KZbin would invent a new super mega like button just for this video. Thanks Paul.

[@Sin00b]

I quickly converted my project to coordinators, and it makes me very happy to split out the navigation from my controllers. My app uses a singleton for networking (I know you don’t like singletons, but I feel like for simple networking across a bunch of views, it actually makes sense, but am open to feedback), and coordinators to move between the different views, usually via button press. I can’t wait to convert over to child coordinators so i can use them in a tabviewcontroller and decouple different tabs out. It’s super clean, thanks for sharing. (BTW, I’m using server side swift for the networking as well, so thanks for teaching me vapor... its a doozy)

[@rikenm]

singleton is fine if there is no state in the singleton class. Networking has no internal state usually.

[@Creimbord]

Thanks for great tutorial, Paul! But I wonder what is the right way to present controller using coordinators? In video code examples you only push view controllers, what if we need to present controller modally?

[@ParthoBiswas007]

I have been following your tutorial recently and I love it. FUN, Informative, and Concise.

[@daniltimofeev6566]

It is really fun, especially when you want modal presentation =)

[@alikiran7329]

So, what's the value of keeping child coordinators in an array and removing them on way back? Navigation controller (actually any parent controller) already tracking child controllers. We can access the relating child coordinator using childcontrollers anyway.

[@jconstant]

Paul, these coordinator videos are fantastic. Thank you! I want to use a coordinator to manage multiple view controllers but in my case, I don't want those view controllers to fill the entire screen when shown because I have a search bar at the top of the screen that should always be displayed. Can this pattern be used to swap view controllers in/out of a Container View?

[@ocannal]

Hello Paul, I think there is problem with the navigating back approach. Let's say we push another viewcontroller in BuyViewController. So didshow will be called again and from controller is BuyViewController, and it will be removed even it's not expected. It's not expected because it's not the child this time, it's parent previous viewcontroller and it's still in the viewcontroller hierarchy.

[@yonataan8]

Thanks for your great tutorials Paul! You're great!

[@serhatt]

When I first saw coordinator I thought it's a good solution for navigation hell. But for this implementation, it adds another complexity into the code base. There are lots of closures, parent-child references going on, another problem is handling the back button. It's kinda good solution to adding removing from an array but when the project grows it won't be flexible and scalable also conforming navigation delegate also adds another complexity for every view controller transition developer should add another if statement for that. In my opinion, the coordinator pattern is not a good solution for navigation instead of solving navigation problem it adds another overhead. If I'm wrong please let me know I may have misunderstood the concept in the first place!

[@rikenm]

I have seen people do a binary search instead of linear search to improve the performance. Closures are optional.

[@TheScrinn]

Hi, thank you for video. I repeat everything what you did but I barely understand how to implement this by myself from scratch. What can I do to understand it better ?

[@amitsamant3875]

Hey paul, great explanation. I have a doubt regarding how to separate networking while using coordinator. for example the BuyViewcontroller takes the product id to buy and the product id has to be fetched from the network on basis of the selectedSegmentIndex so where should we trigger the network call inside the ViewController or Inside the coordinator?

[@DimaJP]

Clear and interesting - very good material.

[@harrylee3943]

The best resource to learn coordinator pattern. I've watched this more than 10 times. This might be a silly question but I am not really sure why we need to keep array of child because in this video, the usage of the array is to just append when child runs and remove when child stops. Can anyone help me to understand?

[@chamorro858]

Awesome job Paul, thank you for covering a lot of coordinator questions that don't seem to be answered on other coordinator tutorials!

[@komunamu]

Thank you Paul for your great tutorial. When we use the coordinator with tabbarcontroller, what is the best way to add the login screen?

[@abdullabardiyev299]

what does "Control the flow in your app" mean if someone knows please help me

[@rajatmishra8121]

Hi Paul, Great video. Thanks for sharing. Learn alot from this tutorial Could you please let me know on what basis should we create sub-coordinators in the app? I mean if we have Login Flow, Home Screen Flow then should we have 2 sub coordinators for them or is there any other factor to consider while considering sub-coordinators? Thank again

[@찬-f2f]

Thank you Paul 😄

[@arekw6012]

Great video! But how to implement a modally presented date picker? When user selects a date from presented view controller, the date must back to the caller. How to do that?

[@Paul-tg8pq]

Thank you for your video! this video is very helpful to me. I have some questions. I can't understand why childCoordinator array exist. Actually, It just added and deleted a coordinator from itself. It doesn't play a role to perform related to transition and so on. When does it use? Why do you use array instead of Dictionary? If we have to use coordinators in array, this is not useful to find and access at once. please, answer my question...

[@daisoreanulaurentiu3943]

Hi Paul, shouldn't we also use a protocol between MainCoordinator and BuyCoordinator?

[@robtea3941]

Interesting, so say I wanted 2 tabs, I would make another coordinator similar to MainCoordinator and add its nav controller to the tabbar viewcontrollers array. In that case every tab had its own instance of UINavigationController. Also, say a tab just had a single view controller, I wouldn't bother with a coordinator in that case and just add it directly to the tab bar viewControllers array

[@charliesoandso]

Oh, I love the tab bar integration. Great video as usual, Paul.

[@TheVirusRko]

Who should handle the navigation bar behaviour? For example if we want the nav bar to be hidden in our "main" or first viewcontroller but when we move to another flow we want to show it? Should it be on every VC? or this must be handle by the coordinator again?

[@davidhughes9320]

How do you present view controllers? This only shows how to push and use navigation controllers. A common case might be presenting a UIAlertController.

[@ahmedabdallah741]

I thought about it and I hope there is a good answer. I solved it by passing the viewController and make the present from the coordinator func buyAnAccount(_ viewcontroller: UIViewController) { let vc = BuyViewController.instantiate() vc.coordinator = self viewcontroller.present(vc , animated: false) }

[@emashawn3734]

Absolutely right about Segues. Although i use storyboards most of the time but i don't use segues as it tightly couples the flow.

[@bscheirman]

Great job Paul! This covers most of the scenarios I've found people ask about when talking about coordinators as well.

[@jeraldo4571]

Should coordinators be on the ViewControllers or it should be owned by the ViewModels?

[@zarzonis]

Awesome explanation on these topics Paul. From now on, I’ll use coordinators.

[@aleph.5811]

so in the child coordinator section, who is responsible for calling buySubscription()? Also, in the BuyViewController, how is it possible to instantiate the navigation stack which needs to reference to what the UIWindow is referencing?

[@WilliamGattoFilho]

3:16

[@goatfacethrilla9367]

Should each coordinator only push a single view to the navigation stack? If another view is required should the coordinator start a coordinator for THAT new view instead?

[@jakyducati]

closures fit just great here

[@burakakyalcin]

yeah but i don't like them taking too much space

[@akshitzaveri224]

When you have many actions, closures degrades the readability and maintanability.

[@estiqueahmedrashel2279]

How to handle back when we want to go to a different ViewController from BuyViewController?

[@bdaralan]

Thank you for a great explanation. Will implement this in my current senior project app.

[@xfabiosoft]

Some video/tutorials about ReSwift and redux on ios?

[@jevoncharles606]

Great video. You have the ability to take something that can be complicated but make it seem simple. I notice that coordinators are a big topic in the community right now. I do like the upsides to them. Do you ever fear there is too many ways that are considered good coding but all do the same thing?

[@deborabarbosa9646]

Is there a way of nagating back with only the mainCoordinator and those 3 viewControllers? (without childCoordinators)

[@SteveHiemstraAKAspeg]

So glad I only know SwiftUI.

[@rgenericson5361]

Then you're seriously missing the boat bro! ; -)

[@kohjiarong6452]

Hi Paul, thanks for providing explanations. It would be great if you could also explain how can we use coordinators to handle different size variants, ie iPad and iPhone variants. Thanks!

[@gabrielsscavalcante]

Thank you again! Great video! I was waiting for this one :)

[@pierogfgenoveseII]

Great video!

[@oguzparlak7857]

Great Job Paul ! It helped me a lot.

[@abanoubghaly7685]

Can anyone tell me the benefits of using an array of child coordinators because I just append and remove them without using their references in the navigation process itself Anyone could help?

[@leftboot13]

I programmatically create my app and use child viewcontrolers. If I understand correctly, I don’t need to worry about implementing “storyboarded”. Is that right? How would you go about configuring a cordinator for this? Create a main coordinator and let all the child view controller‘s talk to that coordinator? Then pass the data as shown? Thanks for the great info once again.

[@gnut1010]

How to handle coordinator if I present ViewController instead of push it

[@maximkrouk1697]

Love the content you do ❤️, definitely gonna buy a few books soon c:

[@salmansiddiqui299]

How to pass data from one coordinator to another?? As we are using common coordinator protocol to start

[@felipefgarcia8969]

Why not have a sample project so we can download and see the implementation, there's no link to github or something like?

[@nickkarpov1]

Awesome!

[@shadealix]

Making any coordinator to be UINavigationViewControllerDelegate has huge cons. Any coordinator which has reference to navigationController can re-assign delegation to itself at any time. And it's brake the logic

[@frantisaulhuamanmera3126]

thanks for sharing Paul.

[@xVinoz]

If you are using storyboards stop and start programatic uikit, thats the industry standard, peace.

[@xVinoz]

ahhh the excessive zoom in the screen is driving me crazy

[@EEGAMINGYT1994]

I am first person to view this video thanks for the video