Summary

Conclusions

Compose describes UI as a function of state. State has an owner, events change it explicitly, and layout adapts elements to the available space. Side effects have a defined lifecycle; domain computations remain independent of composables.

Self-check questions

1. What triggers recomposition?
2. Why is remember not saving to disk?
3. How does the order of padding and background affect the result?
4. Why does a list need a stable key?
5. When does LaunchedEffect cancel its coroutine?
6. What must be checked besides a successful compilation?