# Using LiveView for multi-user / collaborative app development? **URL:** \ **Category:** Questions\ **Tags:** phoenix, use-cases, liveview, collaboration, vaxine\ **Created:** [April 27, 2022, 2:09pm UTC](https://forum.elixirforum.com/t/using-liveview-for-multi-user-collaborative-app-development/47467 "2022-04-27T14:09:03Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![chrismccord](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/chrismccord/32/24233_2.png) [@chrismccord](https://forum.elixirforum.com/u/chrismccord)\ **Post date:** [April 28, 2022, 6:30pm UTC](https://forum.elixirforum.com/t/using-liveview-for-multi-user-collaborative-app-development/47467/8 "2022-04-28T18:30:43Z")
> [@thruflo](#): > > Do you have any insight in particular from visibility into LiveView adoption / thinking through the network-on-the-interaction-path constraint? Obviously offline support is a clear dealbreaker. The interesting thing about that in context of this convo is that Google Docs also doesn’t work offline. It swaps over to read-only mode as soon as the connection dies. I can’t think of many web applications I use day to day that are offline capable. I also maintain that for the vast majority, just because SPAs are _capable_ of offline mode, doesn’t mean folks actually implement it. You opt-in to a massive amount of complexity in doing so. That said, if you need it, you need it, but I find most folks don’t bother implementing it just because they can. So vast majority of web apps today are already on the network-on-the-interaction path. Carrying on working while offline, optimistic updates that require pre-rendering the full UI element before hitting the server, and particularly large HTML documents are all things that would point towards client code rather than LV, bu there’s some gray area. --- _[View the full topic](https://forum.elixirforum.com/t/using-liveview-for-multi-user-collaborative-app-development/47467)._