it's hard to say. stepping back, do you really nee...

# android

[jw]

it's hard to say. stepping back, do you really need to persist the redux store(s)? or are they a function of the persisted state and the behavior of the user? I would recommend persisting the user data in a relational model using SQL Delight (preferably, obviously) or Room (whatever, i mean, if you have to 🤪) and then consuming that into the redux store for modeling the active app state. The redux architecture models the in-memory state, but you would still send mutations to actual persistence asynchronously. So a mutative action would be handled by an effect of some sort which might mutate the redux state but also mark it as not being persisted. The effect would then persist it on a background thread and send an event back to the store to mark it as persisted which would clear that bit and make the state "real".