Your main argument is that saving state between configuration changes takes too much effort.
Guest Contribution
Your main argument is that saving state between configuration changes takes too much effort. But as android developer you know, that your activity can die in other cases as well and you can’t be lazy ass that ruins user experience on low-end phones, which OS needs to free up memory and cannot hold more than 2–3 apps in background. If you check “don’t keep activities” in developer options, you see that all this apps are keeping the state properly even with the screen orientation locked
Handling fragility of activities is easy breeze with modern libraries such as Moxy/Mosby and Architecture Components. Use this powerful tools to make life of all of users easier, not just that ones who rich enough to afford it
Powered by WPeMatico
