A modern programming language that makes developers happier.

kotlinlang

hi all, I am currently working on a data collection app. where user has to fill data in a series of screens and at the last screen we are supposed to make an api call. So we have decided on using viewmodel per screen architecture since we use the same screens for the edit flow as well and store the data filled my user to the Local DB before they move to next screen(This decision is made because we saw significant users facing process death).
If I can keep this simple I have drafts in my localDB which I update at the end of each screen which has only LocalID and not serverID. Though currently we are not actually going for offline support but that is definitely in pipeline so I am looking into store. But I am not sure if store fits to our usecase and if yes how to manage two different keys