4 ms·
Because that capability is required for apps to interoperate. Sandboxing by definition breaks the ability for apps to share data and work together. It's a balan
by izacus 6y ago
Because that capability is required for apps to interoperate. Sandboxing by definition breaks the ability for apps to share data and work together. It's a balance to be struck, a perfectly secure system is a useless system.
In this case it was mostly used to render custom share dialogs (you need to list apps for that), in-line share buttons (checking if other app exists is useful to not show the ones that aren't installed) and some other possible optimizations (e.g. mostly bug fixes for broken apps that couldn't handle types of data).
From developers perspective it's useful because it makes your app more reliable and easy to use. With the downside that malicious people can abuse it.
- uoaei 6y agoI hope you are aware that permission flags can be toggled by the user.
- f6v 6y agoI see absolutely no reason for this. You want to share a picture? Fine! Just specify a content type, and the system will present a list of apps capable of handling it to the user.
- m00x 6y agoIt does add some benefits and can result in a slightly better experience for some apps, but the risk/reward is not worth it at all.
- izacus 6y agoSharing pictures isn't the only use case. The APIs were widely used for quite a few other use-cases as well (this is why it's a permission now and not removed completely). Please remember that but everyone subscribes to your exact model of safety and capability. There are people that want more from their pocket computers than a restricted consumer device.