Dan Tech Academy
After this lesson you will
  • Classify code as a domain contract, a data implementation, or DI wiring
  • Trace LeaderboardRepository into its Supabase implementation, including dispatcher and cache details
  • Choose abstraction names by capability and pick honest unit vs integration test boundaries
Duration6 min
DifficultyIntermediate

Separate Repository Contracts and Data Implementations

Separate domain contracts from backend details.

What this lesson covers
  1. 01Lesson Promise
  2. 02Start With the Domain Need, Not the Backend
  3. 03Trace the Leaderboard Contract Into Data
  4. 04This App Does Not Have a Repository-Only Rule
  5. 05Read Dependency Direction and DI Separately
  6. 06Testability Is a Boundary Benefit, Not Magic
  7. 07Code Reading Path
  8. 08Checkpoint
  9. 09Bad Smells
  10. 10Key Takeaway

Topics: mobile-action-pro, clean-architecture

10 sections left in this lessonUnlock all of Mobile Action ProLesson Promise, Start With the Domain Need, Not the Backend, … — 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