Dan Tech Academy
After this lesson you will
  • Separate the route that owns the wiring from the content composable that only renders state
  • Pass state down and send user intent up through callbacks
  • Tell persistent state apart from one-time events through two separate collection paths
Duration12 min
DifficultyBeginner

Build A Compose Screen From State

The route owns the wiring, and the content composable only renders state. And why shouldn't a Toast live 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 Goes Up
  5. 05Part 4: Gather The Screen Modes In One Place In The Composable
  6. 06Part 5: You Can Still Use Local State
  7. 07Part 6: State And One-Time Events Take Two Different Paths
  8. 08Code Reading Path
  9. 09Bad Smells
  10. 10References
  11. 11Key Takeaways

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 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