In fact, memory cannot analyze how much memory is running in the background, nor is it the main reason why the phone is stuck. You have to compare the memory usage in iOS. It is not less than Android at all, not to mention that the iPhone itself has less memory.
The power consumption of mobile phones is concentrated on the CPU. No matter how much memory you use, it will consume the same amount.
Regarding the scheduling of background applications, the mechanisms of Android and iOS are similar. If the application is full, clear the background program to make space. Programs have priorities, and those with lower priorities will be killed first.
The difference is that Android and iOS have different mechanisms for background programs. iOS only allows a small number of programs to stay in the background, while Android has no restrictions and allows programs to invade the background. In particular, Google has not entered the country. The domestic Android market is in chaos, and there is no market to restrict the behavior of apps. This has promoted the design of Android apps to be arbitrary. Even if some apps do not have the need to stay in the background, they still have to do some tricks to stay in the background. If things go on like this, the mobile phone will be under high load for a long time, which will cause the Android machine to become more and more stuck as it is used.

1, apps will wake up each other + start automatically in the background + prevent themselves from being killed by triggering system events
2, the cache is accumulating, and sometimes the cache of the app can be completely cleared without uninstalling the app
3, the app design is bloated and there is no performance optimization
As for the general principle of Android system memory scheduling, it is not very clear