stateIn creates a StateFlow and not a MutableStateflow, so I think is impossible to update it's value. Since the state of your screen can be changed you should have a MutableStateflow and update it's value when you need to update the screen state. Since the initial loading of the screen is dependent on the userInfoApi data, why is it not good to call it inside the init of the viewmodel?