This is definitely not a web-only issue. I have seen the same issue with convergent KDE apps (Qt UI based). Not an expert in this space but intuitively it feel

This is definitely not a web-only issue. I have seen the same issue with convergent KDE apps (Qt UI based). Not an expert in this space but intuitively it feels that what is missing in a widely adopted heuristic of how to "best", or at least, "least-bad" map the information and interactivity components of a given UI to different screen geometries. It feels like a hard problem to crack: in some cases there might not be a good solution at all. So the heuristic should be able to say "no, what you are trying to do does not match any known Homo Sapiens sensory configurations". Think e.g. how you would map a large and busy DAW screen [1] with hundreds of dials on a small mobile. You'd probably have to rethink the entire workflow, segment into small chunks, smoothly switch screens while providing summaries and connecting elements etc. [1] https://soundcamp.org/music-and-sound-production-blog/best-free-and-open-source-daws-music-recording-and-making https://soundcamp.org/music-and-sound-production-blog/best-f...