Dan Tech Academy
After this lesson you will
  • Read settings.gradle.kts to see the real module graph and spot folders that are not part of the build
  • Explain what :app, :core, :domain, :data, :theme, :ui-components, and :feature:* each own
  • Recognize how modules are declared through convention plugins and classify new code with the 8-question checklist
Duration6 min
DifficultyBeginner

Read the Module Graph

Read a project as a system instead of a pile of folders.

What this lesson covers
  1. 01Lesson Promise
  2. 02Why The Module Graph Comes First
  3. 03Part 1: A Folder Is Not A Module
  4. 04Part 2: Read The Modules By Responsibility
  5. 05Part 3: A Module Name Can Lie About Its Scope
  6. 06Part 4: Understand The App Module
  7. 07Part 5: Understand The Boundary Modules
  8. 08Part 6: Understand UI Ownership
  9. 09Part 7: How A Module Is Declared
  10. 10Part 8: Classify Code Before You Add Code
  11. 11Checkpoint

Topics: mobile-action-pro, architecture-map

11 sections left in this lessonUnlock all of Mobile Action ProLesson Promise, Why The Module Graph Comes 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
Sign in