Reminds me of this discussion where LV forms came up more than once, posting in hope that it adds some value here:)
Kallee
joshamb
A super minor note as I only found out about this a few weeks ago (and this is more for future readers), but this hasn’t been the advice in the docs since 0.20.4 Phoenix.Component — Phoenix LiveView v0.20.4
Instead, you can just use a button
# NEW
<button
type="button"
name="mailing_list[emails_drop][]"
value={ef.index}
phx-click={JS.dispatch("change")}
>
<.icon name="hero-x-mark" class="w-6 h-6 relative top-2" />
</button>
vs
# OLD
<label>
<input type="checkbox" name="mailing_list[emails_drop][]" value={ef.index} class="hidden" />
<.icon name="hero-x-mark" class="w-6 h-6 relative top-2" />
</label>
Also despite this, I think it would still be interesting to see a mockup of your form in a repo, even it it’s just to showcase that having forms of that complexity is just not a good fit for LiveView 
1
tmbb
steffend
Phoenix Core Team
I want to look into this a little bit more when I find the time. I’d appreciate it a lot if you could publish the LiveView version somewhere, as that would save me a lot of time reproducing 
8
tozz
Coming back to this I had a look in Wireshark for my specific payloads in forms, and the compression of most messages were pretty darn insane, which makes sense in a form because almost all the data is identical.
I knew compression helped a lot, but hadn’t looked at this specific type of data before, dumb of me I know, always measure!
3