any suggestion at the moment to optimize this instead?
Personally, I'd just switch to another Archtecture pattern (MVVM) or use an MVI library that does not impose strict rules regarding where you have to do the mapping, and where you have to perform state reduction.
This library for example avoids the (intent -> action) mappings altogether. When you call add you can follow the flow linearly and the state is reduced contextually.
for now the MVFlow is the simplest we can think of at the moment, also I'm fully agreed with you
any suggestion at the moment to optimize this instead?
Personally, I'd just switch to another Archtecture pattern (MVVM) or use an MVI library that does not impose strict rules regarding where you have to do the mapping, and where you have to perform state reduction.
This library for example avoids the (intent -> action) mappings altogether. When you call
add
you can follow the flow linearly and the state is reduced contextually.thanks for the suggestion, the Orbit-MVI 3 seems fit our usecases and a simplified version! ❤️