My obligatory crusade: most apps, including native apps, are just interactive documents and there would be strong benefits to everyone if they moved in that dir

My obligatory crusade: most apps, including native apps, are just interactive documents and there would be strong benefits to everyone if they moved in that direction more explicitly. Some exceptions exist of course. But a surprisingly large number of apps on my computer are just XML trees (or could be represented that way) when you really dig into them. I want my keyboard settings to work the same way in documents and in the vast majority of the applications I run. I want to be able to query pure-text representations of state in applications, not just in documents. With some minor exceptions, I want standardized controls across most of my OS, including in web apps. In regards to privacy, I don't want applications to fingerprint me. I have capabilities that I'd like to turn on for some apps, but I don't want them all to be on by default for every app. The system shouldn't be "you're either static content, or you can do anything you want." All of my privacy/security concerns about documents also apply to apps; most applications I use don't need access to things like fullscreen, NFC, mouse control, etc. Some do, and I want them to work, but I shouldn't need to grant access to every application across the board for that. I think the division between apps and documents is largely fictional; it's a spectrum, not a hard line, and most "apps" are still fundamentally closer to documents than they like to admit, even in their flashy interactive forms with animations and user-state, and could benefit from the same kinds of standardization and sandboxing that documents enjoy. I don't think we should be separating out a category of websites (or native programs for that matter) where we say that anything goes just because they're "apps", I think that masks the problem that sandboxing is a UX/architecture issue everywhere across the entire spectrum.