1. Application wide state is easy since you can always access state from parent components in child components. The problem occurs when you want to update paren

1. Application wide state is easy since you can always access state from parent components in child components. The problem occurs when you want to update parent state from child components. Fortunately, you can make your own abstractions in Concur. For example, you can use a "Wire" - which lets multiple child components share and update parts of the parent's state (https://github.com/purescript-concur/purescript-concur-core/blob/master/src/Concur/Core/Patterns.purs#L117 https://github.com/purescript-concur/purescript-concur-core/...). Note how this abstraction just uses the high level Concur API, and doesn't depend on the UI backend. With a wire the code might look something like this - -- A wire into parent's state, accessible using `with`, and updateable using `wire.send` counter wire = with wire \i -> do button [onClick] [text (show i)] wire.send (i+1) And you can compose several counters that share state like this (the first two counters will increment together - -- Parent component creates a wire using `local` and an initial value local 0 \w -> div [] [ counter w , counter w , some , other , widgets ] -- Beyond this point the local state is gone and can't be accessed doSomethingElse 2. Concur widgets can perform sync effect as well as async effects using `liftEffect` and `liftAffect`, and the results of those actions are available within the monad just like other widget results. Does that answer your question?