After this lesson you will
- Read a DI module as a table that pairs contracts with implementations
- Choose single or factory by asking about lifetime instead of out of habit
- Follow startSharedApp and appKoinModules to see both platforms share one graph
Duration10 min
DifficultyIntermediate
Composition Root: Where Providers Are Defined
You start to see how the code is organized, and you find the one place that knows both the contracts and the implementations, for Android and iOS alike.
- 01Lesson Goal
- 02Part 1: One Module List For Two Platforms
- 03Part 2: single Or factory? The Question Is Lifecycle
- 04Part 3: The Power Of Constructor Injection
- 05Part 4: One Test Locks The Whole Graph
- 06Part 5: Not Everything Needs To Be Provided And Injected
- 07Code Reading Path
- 08Bad Smells
- 09Key Takeaways
Topics: mobile-action-pro, clean-architecture
9 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: One Module List For Two Platforms, … — plus 114 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in