Hahahahah, right.

For properly developed apps that respect user's ownership of a device, and only run when called for by a user, this is true.

The problem is so many apps register for different broadcasts when they simply don't need to be running in the background. For example, why would a bar code/QR code app need to be always active, registering for events like Screen On, when it's something typically rarely used and would launch very quickly anyway.

No, in the real world your claim is booooogus, as evidenced by the hundreds of apps I've fought over this since 2010.

Even today on a current version of Android (and 6GB of ram), I can run an OOM cycle and the phone is far snappier - because the Android defaults around the OOM classes are too relaxed. I've got 6gigs of ram, please keep 1gig clear for starting apps, I have plenty to go around. Instead, the Android default is still too low - last time I looked it still took getting down to 250mb free to auto-start OOM.

Funny thing is, today kicking off OOM isn't as disruptive as it was even 5 years ago. I have hundreds of apps/services, and it no longer disrupts any of them.

All this is also why misbehaving apps are in a secondary user profile, to ensure they don't run unless I call for them (there are other ways/tools, but this is native).

Doing it yourself does more harm than good

Also a myth. A lot of apps really benefit from the ol' force close, maybe with a clear cache for good measure.

Poorly written, possibly vibe coded trash apps, but still.

Looking at you, Samsara Driver app. Holy shit how can you be this bad. Amazing that it's becoming the industry standard for dispatching and logging in the trucking industry. How we hates it, oh yes...