The system partition is a read only partition that gets updated only in firmware updates.
Apps can also be packaged on that partition.
Since you can't delete files from it, you cmhave the ability to disable a system application.
That deletes the updates (which are on the data partition) then disables the app.
Because I thought that was more of a "you pay us to make your app unremovable preinstalled on all of our phones"-thing rather than anything technical.
But what happens is that there isn't any way using just the device to reset it back to factory defaults, and that's a problem now. If your average joe can uninstall the play store by accident, they then can't get it reinstalled again without a PC and some technical knowhow.
By making it so you can only "disable" preinstalled apps, you limit the damage that can be done, and because of partitions you don't really harm the user at all (because that space wouldn't be reclaimed if fully deleted anyway).
It's also why most "preinstalled" apps are now just a 4kb placeholder that makes google play go and download the latest version of the app the second it's connected, so if you "disable" it you are only left with a 4kb "skeleton" of an app there.
Any full uninstall of a system app would require remounting /system as rw.
What is your beef with "disabling"? Under the hood it is the same thing as uninstall, minus the file removal or the actual apk. App doesn't run, has no permissions, is never loaded/mapped into RAM.
Why do Google Apps have to be installed to the system partition anyway?
I have tried several email clients and image viewers from Google's app store, — all of them work fine without being system apps.
Other people already responded and stated the reason, that wasn't directly stated. In addition to those apps being on system read-only partition and not being easy to modify it you should also know that the app doesn't take any extra space from your data partition (obviously, when app is disabled and all its data was cleared)
What is annoying me most are those apps that you can't disable :/ also they could either make it easier to disable or make it diabled by default and on first boot offer user to enable it if they want it, but that won't happen because they want to ham fist those apps to us.
Interesting that you are "blaming" Google for this instead of vendors, when (usually) it vendors who make their crap uninstallable. Or do you see lot of uninstallable stuff in AOSP?
Most of the bloatware problem is, in fact, Google's apps. If you have duplicates on your phone, it's because Samsung or whoever else made their own apps, but were forced to ship Google's anyways.
They're both pre-installed apps that some people might or might not need that you can't uninstall.
It's a super fine line that is basically just preference, and they are both bloatware in a technical sense (can't uninstall it).
> Everyone need not have a single company's apps shoved forcibly down their throats.
So it looks like Apple is shoving their apps down our throats.
And in a world where 85% of phones run Android, do you consider that an upside? That people only have the choice between Apple or Google experiences, and no others?
Point taken and conceded.
Although I'd point out a small subtlety in the matter that they are definitely not mandatorily non-uninstallable on all Android phones, namely those that do not ship Gapps to begin with.
Surely they can't still use the excuse that deleting those apps will "mess with the OEM's image", now that Project Treble exists, and everything can be put into their own separate modules?
If they do use that excuse, I don't buy it. It's likely an internal decision to cater to their partners who don't want their users to uninstall those apps. But it's really a petty move from the OEMs, too, because if I'm willing to disable that app, then I might as well uninstall it, because clearly I don't intend to ever use it.