At the end of the day, regardless if you invoke link/2, live_patch/2,
and live_redirect/2 from the client, or redirect/2, push_patch/2,
and push_redirect/2 from the server, the user will end-up on the same
page. The difference between those is mostly the amount of data sent over
the wire:

• link/2 and redirect/2 do full page reloads

• live_redirect/2 and push_redirect/2 reloads the LiveView but
  keeps the current layout

• live_patch/2 and push_patch/2 updates the current LiveView and
  sends only the minimal diff

An easy rule of thumb is to stick with live_redirect/2 and push_redirect/2
and use the patch helpers only in the cases where you want to minimize the
amount of data sent when navigating within the same LiveView (for example,
if you want to change the sorting of a table while also updating the URL).

Notably, I’ve largely ditched the traditional view structure used by Phoenix controllers / views / templates in favor of:

my_app_web/
  pages/
    shipments/
      show/
        show.html.leex # the template
        show.ex # the live view
        data.ex # a data fetching helper
        view_helper.ex # the normal phoenix view helper
        components/ # components relevant only to this page
          ...

It makes this whole process way easier. I don’t really like Live in the module name anyway, it holds not a lot of value. The shipment show module name would be MyAppWeb.Pages.Shipments.Show, so it gets named just like any other Elixir module. All the files for a page are all in one nice spot, and you can make a new page by just copying and pasting any existing page folder.

I only played briefly with live view, once about a year ago, and once in the past weekend, and I pretty much went for a similar structure, with the only difference being that I didn’t use Pages. This weekend, while experimenting, I used the name Controller for the live view module. So I ended up with something like MySystemWeb.PageA.Controller, MySystemWeb.PageB.Controller, etc.

I find it much saner to navigate through the code, and as you say the things which are frequently read or changed together are in the same place. I also think that the word Live is basically noise. Whether something is a live view or not is imo an implementation detail, and doesn’t belong to the module name.

In the future I plan to do the same thing with controllers. I already did something similar for my blog, but that’s a very simple case so I ended up consolidating everything behind a single controller.