can be adapted for large data. So I think I'll use ViewModels, as my issue was due to the fact that I relied on the
with too much data 😃
1 year ago
Sounds like your complex object should just be persisted to a db, or to a file (remember... you have to worry about process death too) and then you save the state of the id of that complex object.Also, what you read about configChanges is the "old" guidance. I'm sure the official guidance will be updated at some point to include saying that you should override configChanges in a pure compose app.