Dan Tech Academy
After this lesson you will
  • Trace a sign-in request through all eight steps and name what each step does
  • Tell apart a request's DomainResult channel from the session's authState channel
  • Explain why Google Sign-In goes through the GoogleSignInLauncher port with an Android and an iOS implementation
Duration11 min
DifficultyIntermediate

The Clean Architecture Of A Sign-In Tap

Trace auth from the button tap to the session, then the profile sync.

What this lesson covers
  1. 01Lesson Goal
  2. 02Part 1: The Full Map Of One Sign-In
  3. 03Part 2: What Happens After A Successful Login?
  4. 04Part 3: Google Sign-In And The Platform Boundary
  5. 05Part 4: Turning Technical Errors Into Messages For The User
  6. 06Code Reading Path
  7. 07Bad Smells
  8. 08Key Takeaways

Topics: mobile-action-pro, clean-architecture

8 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: The Full Map Of One Sign-In, … — 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
Sign in