The Coordinator Pattern consists of a single class that is responsible for the flow or flows of your application. Typically you will have a root coordinator, who can then use 1 or more sub coordinators as needed. Most of the code is simple instantiation logic, with limited data being passed between view creation methods. With this coordinator you will see a simple but typical implementation, and how we are managing flow within this application.
- [Instructor] We are now ready to start implementing…the coordination pattern within our application.…There's a lot of boilerplate code with the coordinator…so what we've done is we've included a class…within your actual code base.…It's under the Project Files and under the Coordination…there's a file called Root Navigation Coordinator.…We're going to make a group here, we'll call this…Navigation Coordinators.…And we're making an actual group because sometimes…within your application you can have just one coordinator…but it's not uncommon to have many different flows…like a sign-up process or different sections of your app…that you want to be able to navigate to…and they consist of more than one view.…
So sometimes you'll have a root coordinator…and then you'll have a specific coordinator…for those different sections.…And the root coordinator is just in charge of which other…coordinators to trigger or maybe even some single views…to show within there.…So we're going to make an actual group for this.…And we'll just drag and drop it into that group.…
Author
Released
6/27/2017- Moving pieces of architecture
- Designing an MVA app
- Walking through a demo application
- Converting to MVP
- Moving non-view logic to a presenter
- Breaking logic into layers
- Using entities
- Setting up dependency injection
- Implementing the coordination pattern
- Adding data binding with RxSwift
Skill Level Intermediate
Duration
Views
Related Courses
-
Introduction
-
Welcome48s
-
-
1. Moving Pieces of Architecture
-
Why architecture?3m 32s
-
Architecture pieces2m 19s
-
Common architectures3m 42s
-
-
2. Demo Application Walkthrough
-
UI overview41s
-
Code overview1m 18s
-
Load data2m 51s
-
-
3. Convert to MVP
-
Create presenter3m 14s
-
Create presenter, part 23m 28s
-
Create presenter, part 32m 36s
-
Create presenter, part 43m 21s
-
-
4. Expand Layers
-
Expand layers5m 59s
-
Expand layers, part 24m 14s
-
Entities2m 49s
-
-
5. Dependency Injection
-
Swinject overview6m 27s
-
Swinject storyboard3m 14s
-
Presenter conversion5m 45s
-
Protocol injection8m 53s
-
-
6. Navigation Coordinators
-
Coordinator walkthrough3m 15s
-
-
7. Data Binding
-
RxSwift – observables11m 15s
-
RxCocoa – data binding6m 46s
-
-
Conclusion
-
Next steps42s
-
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.
CancelTake notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Coordinator walkthrough