After this lesson you will
- Explain why there are separate row/DTO, domain model and UI state types
- Write pure mappers at the right boundary: data to domain, domain to UI
- Recognize mappers that protect real money and stored data, and pin them with tests
Duration25 min
DifficultyIntermediate
Mapping Between Layers
Mapping Between Layers in the Mobile Action Pro course.
- 01Lesson Goal
- 02Part 1: Three Kinds Of Models, Three Reasons To Change
- 03Part 2: Data To Domain, The Leaderboard
- 04Part 3: Domain To UI, The Leaderboard And The Game Screen
- 05Part 4: A Mapper That Protects Real Money
- 06Part 5: A Storage DTO Is A Contract
- 07Practice Exercise
- 08Code Reading Path
- 09Signs To Avoid
- 10References
- 11Key Points
Topics: kotlin, 06-clean-architecture
11 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: Three Kinds Of Models, Three Reasons To Change, … — 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