each screen has it's own event loop like in the El...

# functional

[tschuchort]

each screen has it's own event loop like in the Elm architecture. Events are fed into the update function which computes the new state and the state is then passed to the view's render function. It's not possible to change the state outside of that cycle so it can't happen that the state is somehow modified at two places at the same time. The question is how to deal with subcomponents/views/widgets/whatever that are stateful too and need access to the parent's state (maybe modify it even). In essence, the service and the list activity are subviews of the app and need to read&write to the list of posts in the app's state. https://hackernoon.com/the-importance-of-state-ownership-in-elm-72f711ceb244