After this lesson you will
- Trace both discovery paths: FeatureRegistry loading Koin modules and FeatureNavigationRegistry loading routes
- Explain why features request navigation through callbacks instead of importing other features
- Debug reflection-based discovery failures using class names and R8 keep rules in proguard-rules.pro
Duration8 min
DifficultyBeginner
Feature Discovery and Navigation Boundaries
Understand why feature modules appear in the app without manual wiring, and how they navigate without coupling.
- 01Lesson Promise
- 02The Big Picture First
- 03Part 1: The First Path, DI Discovery
- 04Part 2: Look Inside A Feature DI Module
- 05Part 3: The Second Path, Navigation Discovery
- 06Part 4: Route Data Lives In :core
- 07Part 5: Callbacks Prevent Sibling Coupling
- 08Part 6: Reflection Is The Easiest Place To Get It Wrong
- 09Part 7: Debug By Behavior
- 10Part 8: Checklist For Adding A New Feature
- 11Anti-Patterns
- 12Checkpoint
Topics: mobile-action-pro, architecture-map
12 sections left in this lessonUnlock all of Mobile Action ProLesson Promise, The Big Picture First, … — plus 64 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in