• Android Side:
On Android, the Play Store does not focus as much on performance optimization, it mainly focuses on security and policy compliance
Because of this, almost all apps can get approved within hours
In theory, all apps can push the hardware to maximum performance and reach the Tjmax temperature limit before hard throttling. This happens on some devices, such as "Qualcomm QRDs, RedMagic devices, rooted phones with custom schedulers and OnePlus phones with battery app removed"
These devices behaves more like Linux PCs rather than typical smartphones, which can result in unnecessary power consumption
This is why OEMs use per-app optimization engines and assign CPU governors or performance profiles based on the app's package name
For example, Android OEMs may assign "Performance Mode" profiles for benchmark apps, rendering apps, ZIP extraction apps, compiler apps and other workloads that require high sustained performance
I am explaining why this is happening:
• Apple side:
iOS can identify which apps are performance or benchmark apps and which are normal apps using app signatures and behaviour analysis
If an app is inefficient or consumes unnecessary power, Apple DOES NOT ALLOW IT on the App Store
This is why App Store verification can take 2–3 times longer compared to the Play Store, as Apple monitors app performance and efficiency more strictly
This is also why Apple restricted JIT (Just-In-Time) compilation, because it can consume additional power and may reduce efficiency
One exception to JIT is SAFARI: Safari's JavaScript engine uses "JIT" because Apple controls the environment (Check the Quote)