Sure except that we already have computers where every app uses the same folder structure, just with some files/folders protected with elevated permissions that aren’t accessible to every app. We already have a solution that works and every desktop OS uses. Why would mobile go for a solution that isn’t actually usable?
The desktop solution isn’t feasible in the mobile context. Even for desktops, you see an increased interest in reproducible/containerized/sandboxed environments with docker, flatpak/snap, immutable operating systems, and so on. It’s all about managing complexity.
All of that interest is from people making computers, or people who manage security. Not from people that use computers as part of their life/work (in contrast to those who’s work is entirely about the computer itself). From a usability standpoint, this type of sandboxing for every app is cumbersome and all it leads to is users finding unsafe work arounds. I used to be able to use my android phone much more as a regular computer than I can now. And I wanted to make a simple app for myself to allow me to automatically copy and catalog photos from my cameras sd card to an external HDD, and I literally cannot do this without jumping through a million permissions and API hoops on Android even though I never plan on publishing this app for others to use. It became such a pain to figure out how to get access to the folders I would need, I just gave up on the entire project. I essentially needed a tool to systematically copy and rename files, and it’s nearly impossible because of these nonsensical policies.
Except when it is not…
For example Boost saves photo is some photo folder somewhere.
The only way i can find anything is using a photo app and scanning my entire phone to find things.
I was being facetious. Yeah, every app saves into a different location. It’s bonkers.
Sandboxing is a good thing. It makes it a lot easier and safer for billions of devices to run millions of apps.
Sure except that we already have computers where every app uses the same folder structure, just with some files/folders protected with elevated permissions that aren’t accessible to every app. We already have a solution that works and every desktop OS uses. Why would mobile go for a solution that isn’t actually usable?
The desktop solution isn’t feasible in the mobile context. Even for desktops, you see an increased interest in reproducible/containerized/sandboxed environments with docker, flatpak/snap, immutable operating systems, and so on. It’s all about managing complexity.
All of that interest is from people making computers, or people who manage security. Not from people that use computers as part of their life/work (in contrast to those who’s work is entirely about the computer itself). From a usability standpoint, this type of sandboxing for every app is cumbersome and all it leads to is users finding unsafe work arounds. I used to be able to use my android phone much more as a regular computer than I can now. And I wanted to make a simple app for myself to allow me to automatically copy and catalog photos from my cameras sd card to an external HDD, and I literally cannot do this without jumping through a million permissions and API hoops on Android even though I never plan on publishing this app for others to use. It became such a pain to figure out how to get access to the folders I would need, I just gave up on the entire project. I essentially needed a tool to systematically copy and rename files, and it’s nearly impossible because of these nonsensical policies.
like the people who make phones for other people to use