> Not a good fit is rather charitable. s/obviously not a good fit/non-starter :) > I think that 'read-only mode' and 'can't interact at all' mode are not the

> Not a good fit is rather charitable. s/obviously not a good fit/non-starter :) > I think that 'read-only mode' and 'can't interact at all' mode are not the same. I agree, but it depends on the application. LiveView doesn't "freeze", but the content on the page is not going to continue updating or be interactive. This indeed limits some applications that want to allow the user to continue editing a document, but your example of a news site absolutely still functions fine for read-only offline. > It becomes totally unresponsive and totally unusable in any offline or high latency situation (trains, stadiums, remote areas) right? Yes, just like the vast vast majority of web applications today, including the vast vast majority of SPAs that could, in theory, work offline, but don't because of the added complexity on the client and server, state syncing, conflict resolution, etc. If working under the offline condition is a hard requirement, LiveView is out full stop. But even for SPAs, this is an opt-in feature today that few choose.