Why are system apps updated in every profile?

gristle-cause

For what reason are auxiliary profiles configured by default to use separate App Store implementations & maintain system apps separately?

I'm under the impression that only one version of a given app can be installed at a time, system wide. If the same App is installed in ProfileA & ProfileB, updating it within ProfileA will automatically update the app installed in ProfileB

If this is true, the default GrapheneOS behavior for multiple user profiles confuses me:

Each profile comes pre-installed with core system apps: Camera, Vanadium, etc. These apps cannot be removed
Each profile - owner included - automatically includes App Store, from which these apps are maintained
The Owner profile is always running, this session cannot be closed while the phone is on

Given this, why are these system apps maintained per-profile, instead of exclusively doing so from the owner profile - much like System Updates are managed? Isnt this just redundancy without any benefit? Is there any reason to enable these automatic updates in every profile?

Novalissoide

gristle-cause I was going to test inducing a conflict by altering 'Release channel' in Private space to 'Stable' for an app, then violate that from Owner which i always keep on 'Alpha' for all available apps. But at present, there isn't any of the apps which represent any difference, they're all up as 'Stable'.

gristle-cause

Novalissoide to test whether the system apps deviate from the expected behavior I outlined, and do allow different versions per profile?

Yeah, that's a good idea. It may be a weaker experiment, but I have a means to test it.

The latest Vanadium update (145.0.7632.109.0) was pushed five days ago. I have a user profile that has not been opened for at least two weeks. Yet, when I enabled airplane mode & opened the profile up, I see that Vanadium has already been updated to 145.0.7632.109.0

Novalissoide

gristle-cause Yes that behaviour is expected. I was curious if the Private space instance of Vanadium, which by android policy will be found updated to the latest since Owner Vanadium got Alpha-updated, but in this case would have the 'local' Private space-setting to not going beyond Stable,
I don't know, will it be embarrassed for not having kept its 'Stable' rule or something? A pop-up excuse for it being in Alpha? 😊

No, really I dont expect anything big, crashing or even glitching. It is similar to when users temporarily shift to Beta or Alpha to get an update, then restore the setting to Stable anew, no drama.