This may be an odd question. Would updating all states versus just one at a time consume more battery? I.e. Could it be that MVI is less battery efficient than MVVM since all states are updated every-time one state changes, rather than only the changed state being updated when it changes?

Yes, I'd expect a higher memory consumption and memory churn in MVI, because of the constant mutation of the state plus all the intent objects/singletons. Hard to tell without profiling if it's that big of a problem for the battery.

Thank you for the input 🙂

Technically, this is not a pitfall of MVI per se rather on the rendering logic. Flutter for instance deals better on UI updates