In a socialist society perhaps this would be less of a concern, but my main gripe with this type of approach is the centralization of data and the havoc it would wreak on digital privacy. As it stands, I can compartmentalize what companies have access to this information or that information, and have exceptions in my security modeling for specific services. If one company has a data breach, that’s more tolerable because they have the minimal amount of data necessary on me and I gave them a unique email and password. If all my apps were combined, then I’m at the mercy of one company to maintain my security, and if there’s a leak then everything is compromised. Additionally, I pick and choose who I trust and what data is exposed to which parties under the individual app per service model. With a super app, if they are spying on metadata or god forbid not using encryption and just reading my messages etc, then they have all of it and I have no protection
I don’t think the idea has to be implemented in this way though. The key difference in my mind is that instead of having each app be its own isolated thing, you treat them more as services with APIs. One way this can be handled at the UI toolkit in the OS that could generate a something like a JSON API for each app based on the UI to query the app. This way apps could be trivially composed into custom UIs and workflows, or even scripted. This would follow the whole Unix philosophy where you have a bunch of utils that can be piped together to produce whatever functionality you need.
In a socialist society perhaps this would be less of a concern, but my main gripe with this type of approach is the centralization of data and the havoc it would wreak on digital privacy. As it stands, I can compartmentalize what companies have access to this information or that information, and have exceptions in my security modeling for specific services. If one company has a data breach, that’s more tolerable because they have the minimal amount of data necessary on me and I gave them a unique email and password. If all my apps were combined, then I’m at the mercy of one company to maintain my security, and if there’s a leak then everything is compromised. Additionally, I pick and choose who I trust and what data is exposed to which parties under the individual app per service model. With a super app, if they are spying on metadata or god forbid not using encryption and just reading my messages etc, then they have all of it and I have no protection
I don’t think the idea has to be implemented in this way though. The key difference in my mind is that instead of having each app be its own isolated thing, you treat them more as services with APIs. One way this can be handled at the UI toolkit in the OS that could generate a something like a JSON API for each app based on the UI to query the app. This way apps could be trivially composed into custom UIs and workflows, or even scripted. This would follow the whole Unix philosophy where you have a bunch of utils that can be piped together to produce whatever functionality you need.