I mostly agree with this. I've been refactoring some "modals" that have 30+ fields. Ultimately, I prefer the idea of subdividing a gigantic web app resource int

I mostly agree with this. I've been refactoring some "modals" that have 30+ fields. Ultimately, I prefer the idea of subdividing a gigantic web app resource into smaller pieces whenever it isn't entirely catastrophic for the UX. For example: /MyResource/123 (all operations happen here as various "Modes") vs /MyResource/123/View /MyResource/123/Export /MyResource/123/EditPropertyA /MyResource/123/EditPropertyB /MyResource/123/Delete etc... This doesn't work for all things, but I mostly build internal admin dashboards when I am doing web development. One other benefit to using full routable pages for your various views is that you can subdivide the work a lot more easily. Assuming you have some common layout/style system (which you absolutely should), you can realistically part out the dev work at the grain of a URL at a time. We still have a few modals, but they are all of the "confirm scary operation XYZ" variety.