yes, quite a bit of lifecycle discussion. It's my ...
# compose
a
yes, quite a bit of lifecycle discussion. It's my goal to have pure-compose activities handle their own config changes, i.e. not tear down and recreate the activity. With a reactive system it's redundant. In many ways you can think of Android's activity recreation as a very coarse-grained reactive rebuild of a UI and compose can do it granularly.
😍 16
k
This is soo good to hear! Looking forward to hear more about these, maybe on backstage podcast one day? Android retrospective: activity lifecycle. 😅 Is your work is research atm or you already started to create these changes? Love to check out if you have suggestions where to look!
a
high level designs for compose, plus work by others on the wider team in the arch components saved state management implementation that I referenced: https://developer.android.com/topic/libraries/architecture/viewmodel-savedstate