Yes and no. The intent of the library is to share state within one stack of LiveViews. So, one parent with children LiveViews. You make a very good point, that the actual intent should be to share state between all different LiveViews! That’s at least how e.g. vuex etc. work. If I have time, I will look into that, but PRs are always much appreciated 
Yes, right now, they would get different stores. You’re right, that should change however. I haven’t thought about that.
I attempted to use GenServer to keep the state in its own process next to the root LiveView process. However, I decided on keeping the state within the root LiveView process instead since if the root LiveView process goes down, there’s no LiveView that could still use the state anyway since all child LiveViews die as well.
However, using GenServer would be a great solution for state management between all LiveViews, not only the individual stacks of LiveViews. This should be the way forward indeed.
