Dan Tech Academy
After this lesson you will
  • Name actions by user intent instead of widget details like OnSignInButtonClicked
  • Define a closed action vocabulary with a sealed interface and know exactly when the compiler protects you
  • Handle request actions, async result actions, dialog orchestration, and one-time UI events
Duration10 min
DifficultyBeginner

Model User Intent with Sealed Actions

Turn UI events into a clear action vocabulary you can log and extend to see the payoff.

What this lesson covers
  1. 01Lesson Goal
  2. 02Part 1: Callbacks and Actions in Kotlin Accelerator
  3. 03Part 2: The Sealed Actions of Menu
  4. 04Part 3: Not Every Action Comes From the User
  5. 05Part 4: Drill 1 - Read the Whole Auth Flow
  6. 06Part 5: Naming Standards
  7. 07Code Reading Path
  8. 08Checkpoint
  9. 09Bad Smells
  10. 10Key Takeaway

Topics: mobile-action-pro, compose-state

10 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: Callbacks and Actions in Kotlin Accelerator, … — 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