3 ms·
GOOG agrees with you, and so do I for the most part. That's the way Android worked until recently. Any app (with storage permissions) could store anything in sh
by anderspitman 6y ago
GOOG agrees with you, and so do I for the most part. That's the way Android worked until recently. Any app (with storage permissions) could store anything in shared locations (except SD cards; those have always had these issues), and could mess with other apps' data in these locations. I'm not saying this isn't a security concern. I'm saying they've thrown the user control baby out with the security concern bath water.
Why not have a designated area where apps can share whatever they want, and warn the user that information there can be seen by any app?
- jlokier 6y ago> Why not have a designated area where apps can share whatever they want, and warn the user that information there can be seen by any app? That would rather defeat the point of something like SyncThing wouldn't it? If someone wants to sync their files in MusicAppX which MusicAppX itself doesn't put in the designated shared area, the person needs their sync software to be able to look into MusicAppX's private files area. This reminds me of a friend who used CAD software on their iPad. Eventually they ran out of cash to keep paying the licence for the CAD. And then discovered there was no way to access their own design files they had created themselves. Because they exist inside a private folder, and the iPad does not (maybe did not, I'm not sure if it's changed) allow people to freely browse and read their own files with a generic file browser or other apps.
- anderspitman 6y agoApps would be designed to use the shared space, or provide the option to the user whether to or not. Not all apps would have to provide this options but I suspect most open source apps would.