currently only my activities follow the state mach...
# functional
t
currently only my activities follow the state machine pattern like in MVI and navigation is simply a side effect in the view. But I thought about how really the app class is the "root" function of the app and should decide what activity to display depending on the state. So I would have a backstack (list of states) in the root state and simply returning a different state in one of the reducer functions (and altering the backstack list) would correspond to navigation. But I doubt it would work, there are many issues: for example, navigation is only possible in activities, so I would have to bring in some navigation framework to do that for me