How is that Bad? Any Activity you have need to have proper lifecycle.
Every UI Toolkit has something similar.
Same events for IOS: https://developer.apple.com/documentation/uikit/app_and_envi...
Every UI Toolkit has something similar.
Same events for IOS: https://developer.apple.com/documentation/uikit/app_and_envi...
it was designed for phones with 4mb of memory that need to serialise their entire state everytime a form (activity) disappears because they don't have enough memory and google were too lazy to implement it in the OS
as a result you need to implement masses of error prone boilerplate crap for each and every activity, and nearly everyone gets it wrong in subtle ways
rotate your screen? better implement that serialisation perfectly else the user will lose state when they rotate their device
a lot of apps just disable features like rotation, because they're too time consuming to implement (and a nightmare to test)
This even led to the point where a huge amount of iOS apps simply banned rotation support to not deal with it.
It's just a different tradeoff. The underlying issue is that developers don't want to deal with storing the state which causes issues on lower end devices, which start to break as users multitask. The Android tools for that also aren't all that great - although I also haven't really seen any other toolkit do it better.
That said, I agree. Rotation should not be conflated with general app suspension. They are two different concerns. iOS does this.
This is literally how iOS and other mobile toolkits work as well.