Coordinators Pattern for Android
summary
Matheus Cassiano explains the Coordinators pattern for Android, focusing on isolating navigation and presentation layers in an app. He describes how to structure components so navigation logic is separated from UI code, using Android-specific patterns and code organization to improve modularity and testability.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:30Traditional navigation problems
- 4:01Fragment limitations
- 6:36Fragment transactions and state
- 8:03Modern navigation alternatives
- 10:54Coordinator concept and benefits
- 13:05What is Coordinator pattern
- 16:19Coordinator benefits
- 18:13Implementing Coordinator
- 21:56Practical Coordinator example
- 23:27Architecture advantages
- 25:14Testability and dependencies
- 26:46Challenges and learning curve
- 28:15Recommendations and best practices
- 29:18Dependency and data injection
- 30:00Resources and next steps
related talks
37mHands on with Coordinators
35mCicerone — MVP Navigation Without Pain or Tears
32mAre you coordinating already?
37mHow to Avoid Chaos: Navigation as a Separate Logical Layer
07mInterview with
47mClean Architecture for Android
46mModern Android: How to ditch Activities and Fragments
48mEfficient Android Layouts