After this lesson you will
- Name actions after 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
- Manage request actions, async result actions, dialog orchestration and one-time UI events
Duration10 min
DifficultyBeginner
Manage User Intent With Sealed Actions
Turn UI events into a clear action vocabulary that you can log and extend yourself to see the payoff.
- 01Lesson Goal
- 02Part 1: Callbacks And Actions In Kotlin Accelerator
- 03Part 2: The Menu's Sealed Actions
- 04Part 3: Not Every Action Comes From The User
- 05Part 4: Drill 1, Read The Whole Auth Flow
- 06Part 5: Naming By The Standard
- 07Code Reading Path
- 08Checkpoint
- 09Bad Smells
- 10Key Takeaways
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 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