I suspect that you might be right about using LiveView for things that are traditionally full, rich client side JS apps. However, it is absolutely awesome for

I suspect that you might be right about using LiveView for things that are traditionally full, rich client side JS apps. However, it is absolutely awesome for the "slightly javascript" case of a lot of UIs. Two examples, from my work: Forms with "live" display of validation errors, using one single set of validation on the backend, rather than the duplicated frontend and backend having to match. It's completely trivial to implement with LiveView. Status displays - We built some development hardware based on a Xilinx Zynq FPGA (FPGA + ARM running Linux) and used LiveView to report a lot of the hardware state - primarily the status of all of the registers. A little fiddling with HTML+CSS for the register widget, but then everything else could not have been easier - render your widget once per register, and rerun that whole thing any time pubsub provides an updated register value.