imo it's the platform's choice to have default-visible or default-sandboxed program outputs and data. while possible, it is fairly non-trivial for iOS apps to

imo it's the platform's choice to have default-visible or default-sandboxed program outputs and data. while possible, it is fairly non-trivial for iOS apps to have read/write access to a shared folder where they can drop arbitrary files, which can then be accessed by other apps, or be discovered by the user. it often requires copious permission negotiation handling codepaths by the developer, and a fearlessness of scary permission-warning dialogs by the end-user. even on modern (commercially popular flavors of) Android which no longer imbibes the "free software" ethos of the linux core the OS was built around, you can't access formerly accessible application sandbox folders without installing third party browsing tools or plugging into a desktop computer to mount the storage, and cross-application sandbox access is similar to iOS. in the "personal computing way" mentioned by the article (even today on desktop environments, less so on MacOS) program outputs are default-visible, and developers have to go out of their way to firewall or obscure or encrypt it from being accessible by the user or other programs using OS-provided pathways. i think this is 100% on the OS + hardware + application platform provider (with Apple as all three on iOS).