> That's the world that exists on mobile, and it's pretty great.
No, it's not. Unless you do some weird hacks that aren't officially guaranteed to work (and now that the old READ_EXTERNAL_STORAGE permission has been fully deprecated, don't result in the most natural UX flow, either), Google's sandboxing on Android has e.g. broken the scenario of using a file manager to open a locally stored HTML file in a browser, because following the official API, the browser won't be able to resolve any relative links to other HTML documents or subresources like images/stylesheets/scripts.
Other multi-file file formats are similarly broken, and this more or less applies to all the sandboxing solutions I'm aware of, no matter whether Android, iOS, Windows, Mac or Linux. The only exception I'm aware of is that the macOS desktop sandboxing has some provisions for handling "related" files that only differ in the file extension, but even that of course doesn't handle all scenarios – the aforementioned HTML file example still wouldn't work for example.
No, it's not. Unless you do some weird hacks that aren't officially guaranteed to work (and now that the old READ_EXTERNAL_STORAGE permission has been fully deprecated, don't result in the most natural UX flow, either), Google's sandboxing on Android has e.g. broken the scenario of using a file manager to open a locally stored HTML file in a browser, because following the official API, the browser won't be able to resolve any relative links to other HTML documents or subresources like images/stylesheets/scripts.
Other multi-file file formats are similarly broken, and this more or less applies to all the sandboxing solutions I'm aware of, no matter whether Android, iOS, Windows, Mac or Linux. The only exception I'm aware of is that the macOS desktop sandboxing has some provisions for handling "related" files that only differ in the file extension, but even that of course doesn't handle all scenarios – the aforementioned HTML file example still wouldn't work for example.