Mastering Navigation With Coordinators
Managing Subflows With Child Coordinators
|1||What Is a Coordinator 08:11|
|2||Adopting the Coordinator Pattern Plus 09:19|
|3||Instantiating View Controllers From a Storyboard Plus 09:05|
|4||Navigating With a Coordinator Plus 10:26|
|5||Adding Flexibility and Dynamism Plus 12:36|
|6||Managing Subflows With Child Coordinators Plus 10:51|
|7||Reducing Complexity With Child Coordinators Plus 09:38|
|8||Working With Navigation Controllers Plus 12:00|
|9||Managing Horizontal and Vertical Flows Plus 10:57|
|10||Switching Between Horizontal and Vertical Flows Plus 11:35|
|11||Combining Horizontal and Vertical Flows Plus 10:02|
|12||Storyboards, XIBs, and Code 05:35|
|13||Dependency Injection and the Coordinator Pattern Plus 08:27|
|14||Working With Tab Bar Controllers Plus 10:19|
|15||The Model-View-ViewModel-Coordinator Pattern Plus 11:02|
|16||MVVM-C and Separation of Concerns Plus 06:32|
|17||Choosing Between Closures and Delegation Plus 08:21|
AppCoordinator class is responsible for navigation. It defines the flow of the application and instantiates the view controllers of the project. View controllers no longer need to worry about navigation, which makes them focused and lightweight. There is a cost to this shift in responsibilities, though. As the project grows, the complexity of the
AppCoordinator class increases.
Purchase Mastering Navigation With Coordinators and access it whenever you want and for as long as you want.
Join Cocoacasts Plus and access every 350+ tutorials including Mastering Navigation With Coordinators.