Yes exactly!
It is only different from LiveView imo in that it is not coupled to the DOM or any UI layer, be it HTML, React, Scenic, or some other VDOM - instead of phx-X events that are synonymous with(coupled too?) the DOM - with (arguably) difficult to reason about bubbling characteristics - the only event Redex cares about is an action with a type and optional payload… your reducers are responsible for translating that action into a state change (like a state machine) - this change can be broadcasted as a diff to wherever, instructing your UI to update! All reducers receive the action - they do not need to act on it though - this is done via pattern matching in elixir as apposed to a switch statement in JS…
Yea I’m using this for React - GitHub - revelrylabs/elixir_react_render: React SSR Framework for Elixir · GitHub - it runs some node processes in a pool on the same server as phoenix for invoking the necessary JS to render the HTML over stdio - its pretty rough - getting it all wired up and everything…and doesn’t help much reducing JS bloat, it has just about the same bloat, now on the server AND the Client 
And dealing with the initial render is a nightmare - like now need my API on localhost to access from within these local node processes to make the initial render worthwhile…
