Dan Tech Academy
After this lesson you will
  • Separate a route that owns wiring from content composables that only render state
  • Pass state down and send user intent back up through callbacks
  • Distinguish persistent state from one-time events through two separate collection paths
Duration12 min
DifficultyBeginner

Compose Screens from State

The route owns the wiring, the content composable only renders state. And why not put a Toast in state?

What this lesson covers
  1. 01Lesson Goal
  2. 02Part 1: A Composable Only Answers "What Is the User Seeing?"
  3. 03Part 2: The Route Owns All the Wiring
  4. 04Part 3: State Goes Down, Intent Comes Up
  5. 05Part 4: Branch Screen Modes in One Place Inside the Composable
  6. 06Part 5: You Can Still Use Local State
  7. 07Part 6: State and One-Time Events Travel Different Paths
  8. 08Code Reading Path
  9. 09Bad Smells
  10. 10References
  11. 11Key Takeaway

Topics: mobile-action-pro, compose-state

11 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: A Composable Only Answers "What Is the User Seeing?", … — 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