It’s not about a core feature, it is about interfacing things like these:
- if they don’t exist on the platform, implement them as a separate app or library
The idea is to decouple common services, such as picture collections, from the low-level Safe API. To stay with the picture example, there should be one format to store them and their groupings (the actual images, accompanied by metadata, and collection to group images), and many apps would need to be able work with that. However, how should we ensure that all of those apps do a good job?
Let’s imagine a new fancy Picture App comes out for posting pictures on the Safe Network. We don’t know if the App is trustworthy, so giving it access to our collection of pictures carries significant risk.
However, if we had a “Safe Pictures” account (sort of like an Instagram account) through an “official” App that we do know is secure, then we could delegate the actual handling of data (add/move/modify/delete, and to ensure the correct format) to this secure App and let the Picture App take pictures in its clever ways or add fancy filters or whatnot. We could, for example, restrict picture apps from deleting or moving existing images by default, and allow those features for only a few select apps.
This would allow users to have a single picture collection (that is, not a separate one for all picture Apps) and still have a line of control between the unsafe app and their precious data.