iOS and Android both support apps opting into keeping their data at rest while locked after first unlock. iOS makes this easier via dedicated data classes.
However, you would be very wrong if you assumed that meant this was better in the iOS ecosystem than the Android ecosystem.
Conversation
Replying to
I believe you are talking about Keyguard-bound keys in android. They don't seem to be equivalent to data class keys in iOS. Keyguard-bound keys are enforced by the OS and it remains in memory to encrypt incoming data while decrypt only when the screen is unlocked.
2
Replying to
They aren't enforced by the OS. They're stored in the TEE (legacy keys) / HSM (StrongBox keys) and have proper integration with user profile unlocking, physical confirmation and other hardware features. Of course quality of implementation will vary but that's always the case.